Unified Downlink Control Information for Beam Management

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A base station may transmit downlink control information that may comprise an indication for an uplink beam management procedure or a downlink beam failure recovery procedure. A wireless device may receive the downlink control information and determine a type of procedure to perform based on the indication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/555,352, titled “Unified DCI Design For Beam Management” and filed on Sep. 7, 2017, the disclosure of which is hereby incorporated by reference in its entirety.

BACKGROUND

In wireless communications, various beam procedures may be performed such as uplink beam management or downlink beam failure recovery. It is desired to improve wireless communications by performing various beam procedures in a more timely and efficient manner.

SUMMARY

The following summary presents a simplified summary of certain features. The summary is not an extensive overview and is not intended to identify key or critical elements.

Systems, apparatuses, and methods are described for communications associated with beam procedures. A base station may determine a type of beam procedure for a wireless device. The type of beam procedure may comprise an uplink beam management procedure or a downlink beam failure recovery procedure. The type of beam procedure may comprise other types of beam procedures, such as a downlink beam management procedure, or any other beam procedure. The base station may transmit, to the wireless device, one or more messages comprising downlink control information (DCI). The DCI may comprise an indication of a type of beam procedure, each of which may be associated with the same DCI format. The wireless device may receive the DCI. The wireless device may determine, based on the indication, a type of beam procedure to perform, for example, which may be without performing blind decoding attempts associated with physical downlink control channel monitoring. After determining the type of beam procedure, the wireless device may perform the determined beam procedure.

These and other features and advantages are described in greater detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in the accompanying drawings. In the drawings, like numerals reference similar elements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing (OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for two carriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink and downlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA) and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in a secondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G core network and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F show examples for architectures of tight interworking between a 5G RAN and a long term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocol structures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNB deployment.

FIG. 15 shows an example of configuration of a synchronization signal burst set.

FIG. 16 shows an example of a random access procedure.

FIG. 17 shows an example of transmitting channel state information reference signals for a beam.

FIG. 18 shows an example of channel state information reference signal mapping.

FIG. 19A and FIG. 19B show examples for radio resource control signaling.

FIG. 20A shows an example of an activation/deactivation of a CSI-RS resources MAC control element.

FIG. 20B shows an example of an activation/deactivation of a CSI-RS command.

FIG. 21 shows an example for downlink beam management.

FIG. 22 shows an example of a beam failure event involving a single transmission and receiving point.

FIG. 23 shows an example of a beam failure event involving multiple transmission and receiving points.

FIG. 24 shows an example arrangement of subframes that may comprise SRS transmissions.

FIG. 25 shows an example of high layer signaling for SRS parameter configuration.

FIG. 26 shows an example for uplink beam management.

FIG. 27 shows an example for downlink beam management.

FIG. 28 shows an example for downlink beam failure recovery.

FIG. 29 shows an example for uplink beam management.

FIG. 30 shows an example for a base station regarding downlink beam management, downlink beam failure recovery, and/or uplink beam management.

FIG. 31 shows an example for a wireless device regarding downlink beam management, downlink beam failure recovery, and/or uplink beam management.

FIG. 32 shows example elements of a computing device that may be used to implement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples of the disclosure. It is to be understood that the examples shown in the drawings and/or discussed herein are non-exclusive and that there are other examples of how the disclosure may be practiced.

Examples may enable operation of carrier aggregation and may be employed in the technical field of multicarrier communication systems. Examples may relate to beam procedures in multicarrier communication systems.

The following acronyms are used throughout the present disclosure, provided below for convenience although other acronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5G 5th generation wireless systems

5GC 5G Core Network ACK Acknowledgement AMF Access and Mobility Management Function

ASIC application-specific integrated circuit BPSK binary phase shift keying CA carrier aggregation CC component carrier CDMA code division multiple access CP cyclic prefix CPLD complex programmable logic devices CSI channel state information CSS common search space CU central unit DC dual connectivity DCI downlink control information DFTS-OFDM discrete Fourier transform spreading OFDM DL downlink DU distributed unit eLTE enhanced LTE eMBB enhanced mobile broadband eNB evolved Node B EPC evolved packet core E-UTRAN evolved-universal terrestrial radio access network FDD frequency division multiplexing FPGA field programmable gate arrays Fs-C Fs-control plane Fs-U Fs-user plane gNB next generation node B HARQ hybrid automatic repeat request HDL hardware description languages ID identifier IE information element LTE long term evolution MAC media access control MCG master cell group MeNB master evolved node B MIB master information block MME mobility management entity mMTC massive machine type communications

NACK Negative Acknowledgement

NAS non-access stratum NG CP next generation control plane core NGC next generation core NG-C NG-control plane NG-U NG-user plane NR MAC new radio MAC NR PDCP new radio PDCP NR PHY new radio physical NR RLC new radio RLC NR RRC new radio RRC NR new radio NSSAI network slice selection assistance information OFDM orthogonal frequency division multiplexing PCC primary component carrier PCell primary cell PDCCH physical downlink control channel PDCP packet data convergence protocol PDU packet data unit PHICH physical HARQ indicator channel PHY physical PLMN public land mobile network PSCell primary secondary cell pTAG primary timing advance group PUCCH physical uplink control channel PUSCH physical uplink shared channel QAM quadrature amplitude modulation QPSK quadrature phase shift keying RA random access RACH random access channel RAN radio access network RAP random access preamble RAR random access response RB resource blocks RBG resource block groups RLC radio link control RRC radio resource control RRM radio resource management RV redundancy version SCC secondary component carrier SCell secondary cell SCG secondary cell group SC-OFDM single carrier-OFDM SDU service data unit SeNB secondary evolved node B SFN system frame number S-GW serving gateway SIB system information block SC-OFDM single carrier orthogonal frequency division multiplexing SRB signaling radio bearer sTAG(s) secondary timing advance group(s) TA timing advance TAG timing advance group TAI tracking area identifier TAT time alignment timer TDD time division duplexing TDMA time division multiple access TTI transmission time interval TB transport block UE user equipment UL uplink UPGW user plane gateway URLLC ultra-reliable low-latency communications VHDL VHSIC hardware description language Xn-C Xn-control plane Xn-U Xn-user plane Xx-C Xx-control plane Xx-U Xx-user plane

Examples may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be used for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example, arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 shows a subcarrier transmitting information symbols. FIG. 1 is shown as an example, and a typical multicarrier OFDM system may include more subcarriers in a carrier. For example, the number of subcarriers in a carrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmission band. As shown in FIG. 1, guard band 106 is between subcarriers 103 and subcarriers 104. The example set of subcarriers A 102 includes subcarriers 103 and subcarriers 104. FIG. 1 also shows an example set of subcarriers B 105. As shown, there is no guard band between any two subcarriers in the example set of subcarriers B 105. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 2 shows an example timing arrangement with transmission time and reception time for two carriers. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers. Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other. Different radio frame structures may be supported for FDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing. Downlink and uplink transmissions may be organized into radio frames 201. In this example, radio frame duration is 10 milliseconds (msec). Other frame durations, for example, in the range of 1 to 100 msec may also be supported. In this example, each 10 msec radio frame 201 may be divided into ten equally sized subframes 202. Other subframe durations such as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) may consist of two or more slots (e.g., slots 206 and 207). For the example of FDD, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 msec interval. Uplink and downlink transmissions may be separated in the frequency domain. A slot may be 7 or 14 OFDM symbols for the same subcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDM symbols for the same subcarrier spacing higher than 60 kHz with normal CP. A slot may include all downlink, all uplink, or a downlink part and an uplink part, and/or alike. Slot aggregation may be supported, for example, data transmission may be scheduled to span one or multiple slots. For example, a mini-slot may start at an OFDM symbol in a subframe. A mini-slot may have a duration of one or more OFDM symbols. Slot(s) may include a plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.

FIG. 3 shows an example of OFDM radio resources. The resource grid structure in time 304 and frequency 305 is shown in FIG. 3. The quantity of downlink subcarriers or RBs may depend, at least in part, on the downlink transmission bandwidth 306 configured in the cell. The smallest radio resource unit may be called a resource element (e.g., 301). Resource elements may be grouped into resource blocks (e.g., 302). Resource blocks may be grouped into larger radio resources called Resource Block Groups (RBG) (e.g., 303). The transmitted signal in slot 206 may be described by one or several resource grids of a plurality of subcarriers and a plurality of OFDM symbols. Resource blocks may be used to describe the mapping of certain physical channels to resource elements. Other pre-defined groupings of physical resource elements may be implemented in the system depending on the radio technology. For example, 24 subcarriers may be grouped as a radio block for a duration of 5 msec. A resource block may correspond to one slot in the time domain and 180 kHz in the frequency domain (for 15 kHz subcarrier bandwidth and 12 subcarriers).

Multiple numerologies may be supported. A numerology may be derived by scaling a basic subcarrier spacing by an integer N. Scalable numerology may allow at least from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15 kHz and scaled numerology with different subcarrier spacing with the same CP overhead may align at a symbol boundary every 1 msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wireless device 406. A communication network 400 may include at least one base station 401 and at least one wireless device 406. The base station 401 may include at least one communication interface 402, one or more processors 403, and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the one or more processors 403. The wireless device 406 may include at least one communication interface 407, one or more processors 408, and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the one or more processors 408. A communication interface 402 in the base station 401 may be configured to engage in communication with a communication interface 407 in the wireless device 406, such as via a communication path that includes at least one wireless link 411. The wireless link 411 may be a bi-directional link. The communication interface 407 in the wireless device 406 may also be configured to engage in communication with the communication interface 402 in the base station 401. The base station 401 and the wireless device 406 may be configured to send and receive data over the wireless link 411 using multiple frequency carriers. Base stations, wireless devices, and other communication devices may include structure and operations of transceiver(s). A transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Examples for radio technology implemented in the communication interfaces 402, 407 and the wireless link 411 are shown in FIG. 1, FIG. 2, FIG. 3, FIG. 5, and associated text. The communication network 400 may comprise any number and/or type of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, internet of things (IoT) devices, hotspots, cellular repeaters, computing devices, and/or, more generally, user equipment (e.g., UE). Although one or more of the above types of devices may be referenced herein (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may comprise any one or more of the above types of devices or similar devices. The communication network 400, and any other network referenced herein, may comprise an LTE network, a 5G network, or any other network for wireless communications. Apparatuses, systems, and/or methods described herein may generally be described as implemented on one or more devices (e.g., wireless device, base station, eNB, gNB, computing device, etc.), in one or more networks, but it will be understood that one or more features and steps may be implemented on any device and/or in any network. As used throughout, the term “base station” may comprise one or more of: a base station, a node, a Node B, a gNB, an eNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a WiFi access point), a computing device, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. As used throughout, the term “wireless device” may comprise one or more of: a UE, a handset, a mobile device, a computing device, a node, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. Any reference to one or more of these terms/devices also considers use of any other term/device mentioned above.

The communications network 400 may comprise Radio Access Network (RAN) architecture. The RAN architecture may comprise one or more RAN nodes that may be a next generation Node B (gNB) (e.g., 401) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g. 406). A RAN node may be a next generation evolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device. The first wireless device may communicate with a gNB over a Uu interface. The second wireless device may communicate with a ng-eNB over a Uu interface. Base station 401 may comprise one or more of a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of wireless devices in RRC_INACTIVE state, distribution function for Non-Access Stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected with each other by means of Xn interface. A gNB or an ng-eNB may be connected by means of NG interfaces to 5G Core Network (5GC). 5GC may comprise one or more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB may be connected to a UPF by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane Protocol Data Units (PDUs) between a RAN node and the UPF. A gNB or an ng-eNB may be connected to an AMF by means of an NG-Control plane (e.g., NG-C) interface. The NG-C interface may provide functions such as NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (if applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, QoS handling for user plane, for example, packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling for mobility between 3^(rd) Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), support of network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. A software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. A firmware interface may include a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether the device is in an operational or a non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or a non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or a nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics in the device, whether the device is in an operational or a non-operational state.

A network may include a multitude of base stations, providing a user plane NR PDCP/NR RLC/NR MAC/NR PHY and control plane (e.g., NR RRC) protocol terminations towards the wireless device. The base station(s) may be interconnected with other base station(s) (e.g., employing an Xn interface). The base stations may also be connected employing, for example, an NG interface to an NGC. FIG. 10A and FIG. 10B show examples for interfaces between a 5G core network (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). For example, the base stations may be interconnected to the NGC control plane (e.g., NG CP) employing the NG-C interface and to the NGC user plane (e.g., UPGW) employing the NG-U interface. The NG interface may support a many-to-many relation between 5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At RRC connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g., TAI), and at RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC); in the uplink, the carrier corresponding to the PCell may be the Uplink Primary Component Carrier (UL PCC). Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC); in the uplink, the carrier corresponding to an SCell may be an Uplink Secondary Component Carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to only one cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context in which it is used). The cell ID may be equally referred to a carrier ID, and cell index may be referred to carrier index. In implementation, the physical cell ID or cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, reference to a first physical cell ID for a first downlink carrier may indicate that the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply to, for example, carrier activation. Reference to a first carrier that is activated may indicate that the cell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining any of the examples. The disclosed mechanisms may be performed if certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. One or more criteria may be satisfied. It may be possible to implement examples that selectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices. Wireless devices may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on its wireless device category and/or capability(ies). A base station may comprise multiple sectors. Reference to a base station communicating with a plurality of wireless devices may indicate that a base station may communicate with a subset of the total wireless devices in a coverage area. A plurality of wireless devices of a given LTE or 5G release, with a given capability and in a given sector of the base station, may be used. The plurality of wireless devices may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices perform based on older releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or more messages (e.g. RRC messages) that may comprise a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. An RRC message may be broadcasted or unicasted to the wireless device. Configuration parameters may comprise common parameters and dedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and NAS; paging initiated by 5GC and/or NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and NG-RAN, which may comprise at least one of addition, modification and release of carrier aggregation; or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may further comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g. intra NR mobility or inter-RAT mobility) and a context transfer; or a wireless device cell selection and reselection and control of cell selection and reselection. Services and/or functions of an RRC sublayer may further comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; or NAS message transfer to/from a core network entity (e.g. AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN/CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (both C/U-planes) for the wireless device; and/or store a UE AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g. NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; transmit/receive of unicast data to/from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell that the wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and information for acquiring any other SI broadcast periodically or provisioned on-demand, i.e. scheduling information. The other SI may either be broadcast, or be provisioned in a dedicated manner, either triggered by a network or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g. MasterInformationBlock and SystemInformationBlockType1). The other SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be employed for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or the RRC_Inactive state, the request may trigger a random-access procedure.

A wireless device may send its radio access capability information which may be static. A base station may request what capabilities for a wireless device to report based on band information. If allowed by a network, a temporary capability restriction request may be sent by the wireless device to signal the limited availability of some capabilities (e.g. due to hardware sharing, interference or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with a network. At RRC connection establishment/re-establishment/handover procedure, one serving cell may provide NAS mobility information, and at RRC connection re-establishment/handover, one serving cell may provide a security input. This cell may be referred to as the PCell. Depending on the capabilities of the wireless device, SCells may be configured to form together with the PCell a set of serving cells. The configured set of serving cells for the wireless device may comprise one PCell and one or more SCells.

The reconfiguration, addition and removal of SCells may be performed by RRC. At intra-NR handover, RRC may also add, remove, or reconfigure SCells for usage with the target PCell. If adding a new SCell, dedicated RRC signaling may be employed to send all required system information of the SCell. In connected mode, wireless devices may not need to acquire broadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS dedicated information may be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g. RBs, MAC main configuration and physical channel configuration) comprising any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the wireless device may perform SCell additions or modification.

An RRC connection establishment (or reestablishment, resume) procedure may be used to establish (or reestablish, resume) an RRC connection. An RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information message from a wireless device to E-UTRAN. The RRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be to transfer measurement results from a wireless device to NG-RAN. The wireless device may initiate a measurement report procedure, for example, after successful security activation. A measurement report message may be employed to transmit measurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture for uplink and downlink signal transmission. FIG. 5A shows an example for an uplink physical channel. The baseband signal representing the physical uplink shared channel may be processed according to the following processes, which may be performed by structures described below. These structures and corresponding functions are shown as examples, however, it is anticipated that other structures and/or functions may be implemented in various examples. The structures and corresponding functions may comprise, for example, one or more scrambling devices 501A and 501B configured to perform scrambling of coded bits in each of the codewords to be transmitted on a physical channel; one or more modulation mappers 502A and 502B configured to perform modulation of scrambled bits to generate complex-valued symbols; a layer mapper 503 configured to perform mapping of the complex-valued modulation symbols onto one or several transmission layers; one or more transform precoders 504A and 504B to generate complex-valued symbols; a precoding device 505 configured to perform precoding of the complex-valued symbols; one or more resource element mappers 506A and 506B configured to perform mapping of precoded complex-valued symbols to resource elements; one or more signal generators 507A and 507B configured to perform the generation of a complex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antenna port; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion to the carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA baseband signal, for example, for each antenna port and/or for the complex-valued physical random access channel (PRACH) baseband signal. For example, the baseband signal, represented as s₁(t), may be split, by a signal splitter 510, into real and imaginary components, Re{s₁(t)} and Im{s₁(t)}, respectively. The real component may be modulated by a modulator 511A, and the imaginary component may be modulated by a modulator 511B. The output signal of the modulator 511A and the output signal of the modulator 511B may be mixed by a mixer 512. The output signal of the mixer 512 may be input to a filtering device 513, and filtering may be employed by the filtering device 513 prior to transmission.

FIG. 5C shows an example structure for downlink transmissions. The baseband signal representing a downlink physical channel may be processed by the following processes, which may be performed by structures described below. These structures and corresponding functions are shown as examples, however, it is anticipated that other structures and/or functions may be implemented in various examples. The structures and corresponding functions may comprise, for example, one or more scrambling devices 531A and 531B configured to perform scrambling of coded bits in each of the codewords to be transmitted on a physical channel; one or more modulation mappers 532A and 532B configured to perform modulation of scrambled bits to generate complex-valued modulation symbols; a layer mapper 533 configured to perform mapping of the complex-valued modulation symbols onto one or several transmission layers; a precoding device 534 configured to perform precoding of the complex-valued modulation symbols on each layer for transmission on the antenna ports; one or more resource element mappers 535A and 535B configured to perform mapping of complex-valued modulation symbols for each antenna port to resource elements; one or more OFDM signal generators 536A and 536B configured to perform the generation of complex-valued time-domain OFDM signal for each antenna port; and/or the like.

FIG. 5D shows an example structure for modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for each antenna port. For example, the baseband signal, represented as s₁ ^((p))(t), may be split, by a signal splitter 520, into real and imaginary components, Re{s₁ ^((p))(t)} and Im{s₁ ^((p))(t)}, respectively. The real component may be modulated by a modulator 521A, and the imaginary component may be modulated by a modulator 521B. The output signal of the modulator 521A and the output signal of the modulator 521B may be mixed by a mixer 522. The output signal of the mixer 522 may be input to a filtering device 523, and filtering may be employed by the filtering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA and multi-connectivity. NR may support multi-connectivity operation, whereby a multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTED may be configured to utilize radio resources provided by multiple schedulers located in multiple gNBs connected via a non-ideal or ideal backhaul over the Xn interface. gNBs involved in multi-connectivity for a certain wireless device may assume two different roles: a gNB may either act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610 or 620). In multi-connectivity, a wireless device may be connected to one master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610 and/or 620). Any one or more of the Master gNB 600 and/or the secondary gNBs 610 and 620 may be a Next Generation (NG) NodeB. The master gNB 600 may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NR PDCP 604 and 605. The secondary gNB may comprise protocol layers NR MAC 611, NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may comprise protocol layers NR MAC 621, NR RLC 622 and 623, and NR PDCP 624. The master gNB 600 may communicate via an interface 606 and/or via an interface 607, the secondary gNB 610 may communicate via an interface 615, and the secondary gNB 620 may communicate via an interface 625. The master gNB 600 may also communicate with the secondary gNB 610 and the secondary gNB 621 via interfaces 608 and 609, respectively, which may include Xn interfaces. For example, the master gNB 600 may communicate via the interface 608, at layer NR PDCP 605, and with the secondary gNB 610 at layer NR RLC 612. The master gNB 600 may communicate via the interface 609, at layer NR PDCP 605, and with the secondary gNB 620 at layer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, for example, if a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are configured. Media Broadcast Multicast Service (MBMS) reception may be included but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particular bearer uses may depend on how the bearer is set up. As an example, three alternatives may exist, an MCG bearer, an SCG bearer, and a split bearer, such as shown in FIG. 6. NR RRC may be located in a master gNB and SRBs may be configured as a MCG bearer type and may use the radio resources of the master gNB. Multi-connectivity may have at least one bearer configured to use radio resources provided by the secondary gNB. Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured with multiple NR MAC entities: e.g., one NR MAC entity for a master gNB, and other NR MAC entities for secondary gNBs. In multi-connectivity, the configured set of serving cells for a wireless device may comprise two subsets: e.g., the Master Cell Group (MCG) including the serving cells of the master gNB, and the Secondary Cell Groups (SCGs) including the serving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier (CC) and one of the UL CCs, for example, named PSCell (or PCell of SCG, or sometimes called PCell), may be configured with PUCCH resources. If the SCG is configured, there may be at least one SCG bearer or one split bearer. If a physical layer problem or a random access problem on a PSCell occurs or is detected, if the maximum number of NR RLC retransmissions has been reached associated with the SCG, or if an access problem on a PSCell during a SCG addition or a SCG change occurs or is detected, then an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG may be stopped, a master gNB may be informed by the wireless device of a SCG failure type, and for a split bearer the DL data transfer over the master gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearer may be configured for the split bearer Like the PCell, a PSCell may not be de-activated. The PSCell may be changed with an SCG change (e.g., with a security key change and a RACH procedure). A direct bearer type may change between a split bearer and an SCG bearer, or a simultaneous configuration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may interact for multi-connectivity. The master gNB may maintain the RRM measurement configuration of the wireless device, and the master gNB may, (e.g., based on received measurement reports, and/or based on traffic conditions and/or bearer types), decide to ask a secondary gNB to provide additional resources (e.g., serving cells) for a wireless device. If a request from the master gNB is received, a secondary gNB may create a container that may result in the configuration of additional serving cells for the wireless device (or the secondary gNB decide that it has no resource available to do so). For wireless device capability coordination, the master gNB may provide some or all of the Active Set (AS) configuration and the wireless device capabilities to the secondary gNB. The master gNB and the secondary gNB may exchange information about a wireless device configuration, such as by employing NR RRC containers (e.g., inter-node messages) carried in Xn messages. The secondary gNB may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the secondary gNB). The secondary gNB may decide which cell is the PSCell within the SCG. The master gNB may or may not change the content of the NR RRC configuration provided by the secondary gNB. In an SCG addition and an SCG SCell addition, the master gNB may provide the latest measurement results for the SCG cell(s). Both a master gNB and a secondary gNBs may know the system frame number (SFN) and subframe offset of each other by operations, administration, and maintenance (OAM) (e.g., for the purpose of discontinuous reception (DRX) alignment and identification of a measurement gap). If adding a new SCG SCell, dedicated NR RRC signaling may be used for sending required system information of the cell for CA, except, for example, for the SFN acquired from an MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entities at a wireless device side. A first MAC entity may comprise a lower layer of an MCG 700, an upper layer of an MCG 718, and one or more intermediate layers of an MCG 719. The lower layer of the MCG 700 may comprise, for example, a paging channel (PCH) 701, a broadcast channel (BCH) 702, a downlink shared channel (DL-SCH) 703, an uplink shared channel (UL-SCH) 704, and a random access channel (RACH) 705. The one or more intermediate layers of the MCG 719 may comprise, for example, one or more hybrid automatic repeat request (HARQ) processes 706, one or more random access control processes 707, multiplexing and/or de-multiplexing processes 709, logical channel prioritization on the uplink processes 710, and a control processes 708 providing control for the above processes in the one or more intermediate layers of the MCG 719. The upper layer of the MCG 718 may comprise, for example, a paging control channel (PCCH) 711, a broadcast control channel (BCCH) 712, a common control channel (CCCH) 713, a dedicated control channel (DCCH) 714, a dedicated traffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upper layer of an SCG 738, and one or more intermediate layers of an SCG 739. The lower layer of the SCG 720 may comprise, for example, a BCH 722, a DL-SCH 723, an UL-SCH 724, and a RACH 725. The one or more intermediate layers of the SCG 739 may comprise, for example, one or more HARQ processes 726, one or more random access control processes 727, multiplexing and/or de-multiplexing processes 729, logical channel prioritization on the uplink processes 730, and a control processes 728 providing control for the above processes in the one or more intermediate layers of the SCG 739. The upper layer of the SCG 738 may comprise, for example, a BCCH 732, a DCCH 714, a DTCH 735, and a MAC control 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in one TAG may use the same timing reference. For a given TAG, a wireless device may use at least one downlink carrier as a timing reference. For a given TAG, a wireless device may synchronize uplink subframe and frame transmission timing of uplink carriers belonging to the same TAG. Serving cells having an uplink to which the same TA applies may correspond to serving cells hosted by the same receiver. A wireless device supporting multiple TAs may support two or more TA groups. One TA group may include the PCell and may be called a primary TAG (pTAG). In a multiple TAG configuration, at least one TA group may not include the PCell and may be called a secondary TAG (sTAG). Carriers within the same TA group may use the same TA value and/or the same timing reference. If DC is configured, cells belonging to a cell group (e.g., MCG or SCG) may be grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprises a PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprises a PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. In Example 3, a pTAG comprises a PCell and an SCell1, and an sTAG1 comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Up to four TAGs may be supported in a cell group (MCG or SCG), and other example TAG configurations may also be provided. In various examples, structures and operations are described for use with a pTAG and an sTAG. Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activated SCell. The PDCCH order may be sent on a scheduling cell of this SCell. If cross carrier scheduling is configured for a cell, the scheduling cell may be different than the cell that is employed for preamble transmission, and the PDCCH order may include an SCell index. At least a non-contention based RA procedure may be supported for SCell(s) assigned to sTAG(s).

FIG. 9 shows an example of random access processes, and a corresponding message flow, in a secondary TAG. A base station, such as an eNB, may transmit an activation command 900 to a wireless device, such as a UE. The activation command 900 may be transmitted to activate an SCell. The base station may also transmit a PDDCH order 901 to the wireless device, which may be transmitted, for example, after the activation command 900. The wireless device may begin to perform a RACH process for the SCell, which may be initiated, for example, after receiving the PDDCH order 901. A wireless device may transmit to the base station (e.g., as part of a RACH process) a preamble 902 (e.g., Msg1), such as a random access preamble (RAP). The preamble 902 may be transmitted in response to the PDCCH order 901. The wireless device may transmit the preamble 902 via an SCell belonging to an sTAG. Preamble transmission for SCells may be controlled by a network using PDCCH format 1A. The base station may send a random access response (RAR) 903 (e.g., Msg2 message) to the wireless device. The RAR 903 may be in response to the preamble 902 transmission via the SCell. The RAR 903 may be addressed to a random access radio network temporary identifier (RA-RNTI) in a PCell common search space (CSS). If the wireless device receives the RAR 903, the RACH process may conclude. The RACH process may conclude, for example, after or in response to the wireless device receiving the RAR 903 from the base station. The wireless device may transmit an uplink transmission 904, for example, after the RACH process. The uplink transmission 904 may comprise uplink packets transmitted via the same SCell used for the preamble 902 transmission.

Initial timing alignment for communications between the wireless device and the base station may be performed through a random access procedure, such as described above regarding FIG. 9. The random access procedure may involve a wireless device, such as a UE, transmitting a random access preamble and a base station, such as an eNB, responding with an initial TA command NTA (amount of timing advance) within a random access response window. The start of the random access preamble may be aligned with the start of a corresponding uplink subframe at the wireless device assuming NTA=0. The eNB may estimate the uplink timing from the random access preamble transmitted by the wireless device. The TA command may be derived by the eNB based on the estimation of the difference between the desired UL timing and the actual UL timing. The wireless device may determine the initial uplink transmission timing relative to the corresponding downlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a serving eNB with RRC signaling. The mechanism for TAG configuration and reconfiguration may be based on RRC signaling. If an eNB performs an SCell addition configuration, the related TAG configuration may be configured for the SCell. An eNB may modify the TAG configuration of an SCell by removing (e.g., releasing) the SCell and adding (e.g., configuring) a new SCell (with the same physical cell ID and frequency) with an updated TAG ID. The new SCell with the updated TAG ID may initially be inactive subsequent to being assigned the updated TAG ID. The eNB may activate the updated new SCell and start scheduling packets on the activated SCell. In some examples, it may not be possible to change the TAG associated with an SCell, but rather, the SCell may need to be removed and a new SCell may need to be added with another TAG. For example, if there is a need to move an SCell from an sTAG to a pTAG, at least one RRC message, such as at least one RRC reconfiguration message, may be sent to the wireless device. The at least one RRC message may be sent to the wireless device to reconfigure TAG configurations, for example, by releasing the SCell and configuring the SCell as a part of the pTAG. If, for example, an SCell is added or configured without a TAG index, the SCell may be explicitly assigned to the pTAG. The PCell may not change its TA group and may be a member of the pTAG.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is only transmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 and earlier, a wireless device may transmit PUCCH information on one cell (e.g., a PCell or a PSCell) to a given eNB. As the number of CA capable wireless devices increase, and as the number of aggregated carriers increase, the number of PUCCHs and the PUCCH payload size may increase. Accommodating the PUCCH transmissions on the PCell may lead to a high PUCCH load on the PCell. A PUCCH on an SCell may be used to offload the PUCCH resource from the PCell. More than one PUCCH may be configured. For example, a PUCCH on a PCell may be configured and another PUCCH on an SCell may be configured. One, two, or more cells may be configured with PUCCH resources for transmitting CSI, acknowledgment (ACK), and/or non-acknowledgment (NACK) to a base station. Cells may be grouped into multiple PUCCH groups, and one or more cell within a group may be configured with a PUCCH. In some examples, one SCell may belong to one PUCCH group. SCells with a configured PUCCH transmitted to a base station may be called a PUCCH SCell, and a cell group with a common PUCCH resource transmitted to the same base station may be called a PUCCH group.

A MAC entity may have a configurable timer, for example, timeAlignmentTimer, per TAG. The timeAlignmentTimer may be used to control how long the MAC entity considers the serving cells belonging to the associated TAG to be uplink time aligned. If a Timing Advance Command MAC control element is received, the MAC entity may apply the Timing Advance Command for the indicated TAG; and/or the MAC entity may start or restart the timeAlignmentTimer associated with a TAG that may be indicated by the Timing Advance Command MAC control element. If a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG, the MAC entity may apply the Timing Advance Command for this TAG and/or start or restart the timeAlignmentTimer associated with this TAG. Additionally or alternatively, if the Random Access Preamble is not selected by the MAC entity, the MAC entity may apply the Timing Advance Command for this TAG and/or start or restart the timeAlignmentTimer associated with this TAG. If the timeAlignmentTimer associated with this TAG is not running, the Timing Advance Command for this TAG may be used, and the timeAlignmentTimer associated with this TAG may be started. If the contention resolution is not successful, a timeAlignmentTimer associated with this TAG may be stopped. If the contention resolution is successful, the MAC entity may ignore the received Timing Advance Command. The MAC entity may determine whether the contention resolution is successful or whether the contention resolution is not successful.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G core network (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A base station, such as a gNB 1020, may be interconnected to an NGC 1010 control plane employing an NG-C interface. The base station, for example, the gNB 1020, may also be interconnected to an NGC 1010 user plane (e.g., UPGW) employing an NG-U interface. As another example, a base station, such as an eLTE eNB 1040, may be interconnected to an NGC 1030 control plane employing an NG-C interface. The base station, for example, the eLTE eNB 1040, may also be interconnected to an NGC 1030 user plane (e.g., UPGW) employing an NG-U interface. An NG interface may support a many-to-many relation between 5G core networks and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F are examples for architectures of tight interworking between a 5G RAN and an LTE RAN. The tight interworking may enable a multiple receiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED state to be configured to utilize radio resources provided by two schedulers located in two base stations (e.g., an eLTE eNB and a gNB). The two base stations may be connected via a non-ideal or ideal backhaul over the Xx interface between an LTE eNB and a gNB, or over the Xn interface between an eLTE eNB and a gNB. Base stations involved in tight interworking for a certain wireless device may assume different roles. For example, a base station may act as a master base station or a base station may act as a secondary base station. In tight interworking, a wireless device may be connected to both a master base station and a secondary base station. Mechanisms implemented in tight interworking may be extended to cover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, which may be connected to EPC nodes 1101A or 1101B, respectively. This connection to EPC nodes may be, for example, to an MME via the S1-C interface and/or to an S-GW via the S1-U interface. A secondary base station may be a gNB 1103A or a gNB 1103B, either or both of which may be a non-standalone node having a control plane connection via an Xx-C interface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B). In the tight interworking architecture of FIG. 11A, a user plane for a gNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC 1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-U interface between the LTE eNB and the gNB, and via an S1-U interface between the LTE eNB and the S-GW. In the architecture of FIG. 11B, a user plane for a gNB (e.g., the gNB 1103B) may be connected directly to an S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB and the S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may be connected to NGC nodes 1101C or 1101D, respectively. This connection to NGC nodes may be, for example, to a control plane core node via the NG-C interface and/or to a user plane core node via the NG-U interface. A secondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D, either or both of which may be a non-standalone node having a control plane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C or the gNB 1103D). In the tight interworking architecture of FIG. 11C, a user plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connected to a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., the gNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, and via an NG-U interface between the gNB and the user plane core node. In the architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., the eLTE eNB 1102D) may be connected directly to a user plane core node (e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and the user plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F, which may be connected to NGC nodes 1101E or 1101F, respectively. This connection to NGC nodes may be, for example, to a control plane core node via the NG-C interface and/or to a user plane core node via the NG-U interface. A secondary base station may be a gNB 1103E or a gNB 1103F, either or both of which may be a non-standalone node having a control plane connection via an Xn-C interface to an eLTE eNB (e.g., the eLTE eNB 1102E or the eLTE eNB 1102F). In the tight interworking architecture of FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E) may be connected to a user plane core node (e.g., the NGC 1101E) through an eLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface between the eLTE eNB and the gNB, and via an NG-U interface between the eLTE eNB and the user plane core node. In the architecture of FIG. 11F, a user plane for a gNB (e.g., the gNB 1103F) may be connected directly to a user plane core node (e.g., the NGC 1101F) via an NG-U interface between the gNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocol structures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A may be an S1 secondary base station. An example for a radio protocol architecture for a split bearer and an SCG bearer is shown. The LTE eNB 1201A may be connected to an EPC with a non-standalone gNB 1210A, via an Xx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB 1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A, and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with the PDCP 1205A, and a split bearer type may interface with the PDCP 1206A. The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A and NR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface with the NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B may be an NG secondary base station. An example for a radio protocol architecture for a split bearer and an SCG bearer is shown. The gNB 1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B, via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB 1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC 1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type may interface with the NR PDCP 1205B, and a split bearer type may interface with the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layers MAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer type may interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C may be an NG secondary base station. An example for a radio protocol architecture for a split bearer and an SCG bearer is shown. The eLTE eNB 1201C may be connected to an NGC with a non-standalone gNB 1210C, via an Xn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB 1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C, and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with the PDCP 1205C, and a split bearer type may interface with the PDCP 1206C. The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C and NR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface with the NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particular bearer uses may depend on how the bearer is setup. At least three alternatives may exist, for example, an MCG bearer, an SCG bearer, and a split bearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NR RRC may be located in a master base station, and the SRBs may be configured as an MCG bearer type and may use the radio resources of the master base station. Tight interworking may have at least one bearer configured to use radio resources provided by the secondary base station. Tight interworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., one MAC entity for a master base station, and one MAC entity for a secondary base station. In tight interworking, the configured set of serving cells for a wireless device may comprise of two subsets: e.g., the Master Cell Group (MCG) including the serving cells of the master base station, and the Secondary Cell Group (SCG) including the serving cells of the secondary base station.

At least one cell in a SCG may have a configured UL CC and one of them, for example, a PSCell (or the PCell of the SCG, which may also be called a PCell), is configured with PUCCH resources. If the SCG is configured, there may be at least one SCG bearer or one split bearer. If one or more of a physical layer problem or a random access problem is detected on a PSCell, if the maximum number of (NR) RLC retransmissions associated with the SCG has been reached, and/or if an access problem on a PSCell during an SCG addition or during an SCG change is detected, then: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG may be stopped, a master base station may be informed by the wireless device of a SCG failure type, and/or for a split bearer the DL data transfer over the master base station may be maintained. The RLC AM bearer may be configured for the split bearer Like the PCell, a PSCell may not be de-activated. A PSCell may be changed with an SCG change, for example, with security key change and a RACH procedure. A direct bearer type change, between a split bearer and an SCG bearer, may not be supported. Simultaneous configuration of an SCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. The master base station may maintain the RRM measurement configuration of the wireless device. The master base station may determine to ask a secondary base station to provide additional resources (e.g., serving cells) for a wireless device. This determination may be based on, for example, received measurement reports, traffic conditions, and/or bearer types. If a request from the master base station is received, a secondary base station may create a container that may result in the configuration of additional serving cells for the wireless device, or the secondary base station may determine that it has no resource available to do so. The master base station may provide at least part of the AS configuration and the wireless device capabilities to the secondary base station, for example, for wireless device capability coordination. The master base station and the secondary base station may exchange information about a wireless device configuration such as by using RRC containers (e.g., inter-node messages) carried in Xn or Xx messages. The secondary base station may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the secondary base station). The secondary base station may determine which cell is the PSCell within the SCG. The master base station may not change the content of the RRC configuration provided by the secondary base station. If an SCG is added and/or an SCG SCell is added, the master base station may provide the latest measurement results for the SCG cell(s). Either or both of a master base station and a secondary base station may know the SFN and subframe offset of each other by OAM, (e.g., for the purpose of DRX alignment and identification of a measurement gap). If a new SCG SCell is added, dedicated RRC signaling may be used for sending required system information of the cell, such as for CA, except, for example, for the SFN acquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 and a core 1310 may interface with other nodes via RAN-CN interfaces. In a non-centralized deployment example, the full protocol stack (e.g., NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node, such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304. These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTE eNB 1304) may interface with one of more of each other via a respective inter-BS interface. In a centralized deployment example, upper layers of a gNB may be located in a Central Unit (CU) 1311, and lower layers of the gNB may be located in Distributed Units (DU) 1312, 1313, and 1314. The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs 1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide a control plane connection over the Fs interface, and the Fs-U may provide a user plane connection over the Fs interface. In the centralized deployment, different functional split options between the CU 1311 and the DUs 1312, 1313, and 1314 may be possible by locating different protocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312, 1313, and 1314. The functional split may support flexibility to move the RAN functions between the CU 1311 and the DUs 1312, 1313, and 1314 depending on service requirements and/or network environments. The functional split option may change during operation (e.g., after the Fs interface setup procedure), or the functional split option may change only in the Fs setup procedure (e.g., the functional split option may be static during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of a centralized gNB deployment. Element numerals that are followed by “A” or “B” designations in FIG. 14 may represent the same elements in different traffic flows, for example, either receiving data (e.g., data 1402A) or sending data (e.g., 1402B). In the split option example 1, an NR RRC 1401 may be in a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising a High NR RLC 1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprising a High NR MAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g., comprising a High NR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410 may be in a DU. In the split option example 2, the NR RRC 1401 and the NR PDCP 1403 may be in a CU, and the NR RLC, the NR MAC, the NR PHY, and the RF 1410 may be in a DU. In the split option example 3, the NR RRC 1401, the NR PDCP 1403, and a partial function of the NR RLC (e.g., the High NR RLC 1404) may be in a CU, and the other partial function of the NR RLC (e.g., the Low NR RLC 1405), the NR MAC, the NR PHY, and the RF 1410 may be in a DU. In the split option example 4, the NR RRC 1401, the NR PDCP 1403, and the NR RLC may be in a CU, and the NR MAC, the NR PHY, and the RF 1410 may be in a DU. In the split option example 5, the NR RRC 1401, the NR PDCP 1403, the NR RLC, and a partial function of the NR MAC (e.g., the High NR MAC 1406) may be in a CU, and the other partial function of the NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and the RF 1410 may be in a DU. In the split option example 6, the NR RRC 1401, the NR PDCP 1403, the NR RLC, and the NR MAC may be in CU, and the NR PHY and the RF 1410 may be in a DU. In the split option example 7, the NR RRC 1401, the NR PDCP 1403, the NR RLC, the NR MAC, and a partial function of the NR PHY (e.g., the High NR PHY 1408) may be in a CU, and the other partial function of the NR PHY (e.g., the Low NR PHY 1409) and the RF 1410 may be in a DU. In the split option example 8, the NR RRC 1401, the NR PDCP 1403, the NR RLC, the NR MAC, and the NR PHY may be in a CU, and the RF 1410 may be in a DU.

The functional split may be configured per CU, per DU, per wireless device, per bearer, per slice, and/or with other granularities. In a per CU split, a CU may have a fixed split, and DUs may be configured to match the split option of the CU. In a per DU split, each DU may be configured with a different split, and a CU may provide different split options for different DUs. In a per wireless device split, a gNB (e.g., a CU and a DU) may provide different split options for different wireless devices. In a per bearer split, different split options may be utilized for different bearer types. In a per slice splice, different split options may be used for different slices.

A new radio access network (new RAN) may support different network slices, which may allow differentiated treatment customized to support different service requirements with end to end scope. The new RAN may provide a differentiated handling of traffic for different network slices that may be pre-configured, and the new RAN may allow a single RAN node to support multiple slices. The new RAN may support selection of a RAN part for a given network slice, for example, by one or more slice ID(s) or NSSAI(s) provided by a wireless device or provided by an NGC (e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one or more of pre-configured network slices in a PLMN. For an initial attach, a wireless device may provide a slice ID and/or an NSSAI, and a RAN node (e.g., a gNB) may use the slice ID or the NSSAI for routing an initial NAS signaling to an NGC control plane function (e.g., an NG CP). If a wireless device does not provide any slice ID or NSSAI, a RAN node may send a NAS signaling to a default NGC control plane function. For subsequent accesses, the wireless device may provide a temporary ID for a slice identification, which may be assigned by the NGC control plane function, to enable a RAN node to route the NAS message to a relevant NGC control plane function. The new RAN may support resource isolation between slices. If the RAN resource isolation is implemented, shortage of shared resources in one slice does not cause a break in a service level agreement for another slice.

The amount of data traffic carried over networks is expected to increase for many years to come. The number of users and/or devices is increasing and each user/device accesses an increasing number and variety of services, for example, video delivery, large files, and images. This requires not only high capacity in the network, but also provisioning very high data rates to meet customers' expectations on interactivity and responsiveness. More spectrum may be required for network operators to meet the increasing demand. Considering user expectations of high data rates along with seamless mobility, it is beneficial that more spectrum be made available for deploying macro cells as well as small cells for communication systems.

Striving to meet the market demands, there has been increasing interest from operators in deploying some complementary access utilizing unlicensed spectrum to meet the traffic growth. This is exemplified by the large number of operator-deployed Wi-Fi networks and the 3GPP standardization of LTE/WLAN interworking solutions. This interest indicates that unlicensed spectrum, if present, may be an effective complement to licensed spectrum for network operators, for example, to help address the traffic explosion in some examples, such as hotspot areas. Licensed Assisted Access (LAA) offers an alternative for operators to make use of unlicensed spectrum, for example, if managing one radio network, offering new possibilities for optimizing the network's efficiency.

Listen-before-talk (clear channel assessment) may be implemented for transmission in an LAA cell. In a listen-before-talk (LBT) procedure, equipment may apply a clear channel assessment (CCA) check before using the channel. For example, the CCA may utilize at least energy detection to determine the presence or absence of other signals on a channel to determine if a channel is occupied or clear, respectively. For example, European and Japanese regulations mandate the usage of LBT in the unlicensed bands. Apart from regulatory requirements, carrier sensing via LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals to be transmitted from the beginning of a discontinuous LAA downlink transmission. Channel reservation may be enabled by the transmission of signals, by an LAA node, after gaining channel access, for example, via a successful LBT operation, so that other nodes that receive the transmitted signal with energy above a certain threshold sense the channel to be occupied. Functions that may need to be supported by one or more signals for LAA operation with discontinuous downlink transmission may include one or more of the following: detection of the LAA downlink transmission (including cell identification) by wireless devices, time synchronization of wireless devices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-A carrier aggregation timing relationships across serving cells aggregated by CA. This may not indicate that the eNB transmissions may start only at the subframe boundary. LAA may support transmitting PDSCH if not all OFDM symbols are available for transmission in a subframe according to LBT. Delivery of necessary control information for the PDSCH may also be supported.

LBT procedures may be employed for fair and friendly coexistence of LAA with other operators and technologies operating in unlicensed spectrum. LBT procedures on a node attempting to transmit on a carrier in unlicensed spectrum may require the node to perform a clear channel assessment to determine if the channel is free for use. An LBT procedure may involve at least energy detection to determine if the channel is being used. For example, regulatory requirements in some regions, for example, in Europe, specify an energy detection threshold such that if a node receives energy greater than this threshold, the node assumes that the channel is not free. Nodes may follow such regulatory requirements. A node may optionally use a lower threshold for energy detection than that specified by regulatory requirements. LAA may employ a mechanism to adaptively change the energy detection threshold, for example, LAA may employ a mechanism to adaptively lower the energy detection threshold from an upper bound. Adaptation mechanism may not preclude static or semi-static setting of the threshold. A Category 4 LBT mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, in some implementations, in some situations, and/or in some frequencies, no LBT procedure may performed by the transmitting entity. For example, Category 2 (e.g., LBT without random back-off) may be implemented. The duration of time that the channel is sensed to be idle before the transmitting entity transmits may be deterministic. For example, Category 3 (e.g., LBT with random back-off with a contention window of fixed size) may be implemented. The LBT procedure may have the following procedure as one of its components. The transmitting entity may draw a random number N within a contention window. The size of the contention window may be specified by the minimum and maximum value of N. The size of the contention window may be fixed. The random number N may be employed in the LBT procedure to determine the duration of time that the channel is sensed to be idle, for example, before the transmitting entity transmits on the channel. For example, Category 4 (e.g., LBT with random back-off with a contention window of variable size) may be implemented. The transmitting entity may draw a random number N within a contention window. The size of contention window may be specified by the minimum and maximum value of N. The transmitting entity may vary the size of the contention window if drawing the random number N. The random number N may be used in the LBT procedure to determine the duration of time that the channel is sensed to be idle, for example, before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme may be different from the DL LBT scheme, for example, by using different LBT mechanisms or parameters. These differences in schemes may be due to the LAA UL being based on scheduled access, which may affect a wireless device's channel contention opportunities. Other considerations motivating a different UL LBT scheme may include, but are not limited to, multiplexing of multiple wireless devices in a single subframe.

LAA may use uplink LBT at the wireless device. The UL LBT scheme may be different from the DL LBT scheme, for example, by using different LBT mechanisms or parameters. These differences in schemes may be due to the LAA UL being based on scheduled access, which may affect a wireless device's channel contention opportunities. Other considerations motivating a different UL LBT scheme may include, but are not limited to, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DL transmitting node, for example, with no transmission immediately before or after from the same node on the same CC. An UL transmission burst from a wireless device perspective may be a continuous transmission from a wireless device, for example, with no transmission immediately before or after from the same wireless device on the same CC. A UL transmission burst may be defined from a wireless device perspective or from an eNB perspective. If an eNB is operating DL and UL LAA over the same unlicensed carrier, DL transmission burst(s) and UL transmission burst(s) on LAA may be scheduled in a TDM manner over the same unlicensed carrier. An instant in time may be part of a DL transmission burst or part of an UL transmission burst.

A base station may transmit a plurality of beams to a wireless device. A serving beam may be determined, from the plurality of beams, for the wireless communications between the base station and the wireless device. One or more candidate beams may also be determined, from the plurality of beams, for providing the wireless communications if a beam failure event occurs, for example, such that the serving beam becomes unable to provide the desired communications. One or more candidate beams may be determined by a wireless device and/or by a base station. By determining and configuring a candidate beam, the wireless device and base station may continue wireless communications if the serving beam experiences a beam failure event.

Single beam and multi-beam operations may be supported, for example, in a NR (New Radio) system. In a multi-beam example, a base station (e.g., gNB) may perform a downlink beam sweep to provide coverage for downlink Synchronization Signals (SSs) and common control channels. Wireless devices may perform uplink beam sweeps for uplink direction to access a cell. For a single beam, a base station may configure time-repetition within one SS block. This time-repetition may comprise, for example, one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), or a physical broadcast channel (PBCH). These signals may be in a wide beam. In a multi-beam example, a base station may configure one or more of these signals and physical channels, such as in an SS block, in multiple beams. A wireless device may identify, for example, from an SS block, an OFDM symbol index, a slot index in a radio frame, and a radio frame number from an SS block.

In an RRC_INACTIVE state or in an RRC_IDLE state, a wireless device may assume that SS blocks form an SS burst and an SS burst set. An SS burst set may have a given periodicity. SS blocks may be transmitted together in multiple beams (e.g., in multiple beam examples) to form an SS burst. One or more SS blocks may be transmitted via one beam. A beam may have a steering direction. If multiple SS bursts transmit beams, these SS bursts together may form an SS burst set, such as shown in FIG. 15. A base station 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to 1502H during time periods 1503. A plurality of these SS bursts may comprise an SS burst set, such as an SS burst set 1504 (e.g., SS bursts 1502A and 1502E). An SS burst set may comprise any number of a plurality of SS bursts 1502A to 1502H. Each SS burst within an SS burst set may transmitted at a fixed or variable periodicity during time periods 1503.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may be repeated for a cell, for example, to support cell selection, cell reselection, and/or initial access procedures. For an SS burst, an associated PBCH or a physical downlink shared channel (PDSCH) scheduling system information may be broadcasted by a base station to multiple wireless devices. The PDSCH may be indicated by a physical downlink control channel (PDCCH) in a common search space. The system information may comprise system information block type 2 (SIB2). SIB2 may carry a physical random access channel (PRACH) configuration for a beam. For a beam, a base station (e.g., a gNB in NR) may have a RACH configuration which may include a PRACH preamble pool, time and/or frequency radio resources, and other power related parameters. A wireless device may use a PRACH preamble from a RACH configuration to initiate a contention-based RACH procedure or a contention-free RACH procedure. A wireless device may perform a 4-step RACH procedure, which may be a contention-based RACH procedure or a contention-free RACH procedure. The wireless device may select a beam associated with an SS block that may have the best receiving signal quality. The wireless device may successfully detect a cell identifier that may be associated with the cell and decode system information with a RACH configuration. The wireless device may use one PRACH preamble and select one PRACH resource from RACH resources indicated by the system information associated with the selected beam. A PRACH resource may comprise at least one of: a PRACH index indicating a PRACH preamble, a PRACH format, a PRACH numerology, time and/or frequency radio resource allocation, power setting of a PRACH transmission, and/or other radio resource parameters. For a contention-free RACH procedure, the PRACH preamble and resource may be indicated in a DCI or other high layer signaling.

FIG. 16 shows an example of a random access procedure (e.g., via a RACH) that may include sending, by a base station, one or more SS blocks. A wireless device 1620 (e.g., a UE) may transmit one or more preambles to a base station 1621 (e.g., a gNB in NR). Each preamble transmission by the wireless device may be associated with a separate random access procedure, such as shown in FIG. 16. The random access procedure may begin at step 1601 with a base station 1621 (e.g., a gNB in NR) sending a first SS block to a wireless device 1621 (e.g., a UE). Any of the SS blocks may comprise one or more of a PSS, SSS, tertiary synchronization signal (TSS), or PBCH signal. The first SS block in step 1601 may be associated with a first PRACH configuration. At step 1602, the base station 1621 may send to the wireless device 1620 a second SS block that may be associated with a second PRACH configuration. At step 1603, the base station 1621 may send to the wireless device 1620 a third SS block that may be associated with a third PRACH configuration. At step 1604, the base station 1621 may send to the wireless device 1620 a fourth SS block that may be associated with a fourth PRACH configuration. Any number of SS blocks may be sent in the same manner in addition to, or replacing, steps 1603 and 1604. An SS burst may comprise any number of SS blocks. For example, SS burst 1610 comprises the three SS blocks sent during steps 1602-1604.

The wireless device 1620 may send to the base station 1621 a preamble, at step 1605, for example, after or in response to receiving one or more SS blocks or SS bursts. The preamble may comprise a PRACH preamble, and may be referred to as RA Msg 1. The PRACH preamble may be transmitted in step 1605 according to or based on a PRACH configuration that may be received in an SS block (e.g., one of the SS blocks from steps 1601-1604) that may be determined to be the best SS block beam. The wireless device 1620 may determine a best SS block beam from among SS blocks it may receive prior to sending the PRACH preamble. The base station 1621 may send a random access response (RAR), which may be referred to as RA Msg2, at step 1606, for example, after or in response to receiving the PRACH preamble. The RAR may be transmitted in step 1606 via a DL beam that corresponds to the SS block beam associated with the PRACH configuration. The base station 1621 may determine the best SS block beam from among SS blocks it previously sent prior to receiving the PRACH preamble. The base station 1621 may receive the PRACH preamble according to or based on the PRACH configuration associated with the best SS block beam.

The wireless device 1620 may send to the base station 1621 an RRCConnectionRequest and/or RRCConnectionResumeRequest message, which may be referred to as RA Msg3, at step 1607, for example, after or in response to receiving the RAR. The base station 1621 may send to the wireless device 1620 an RRCConnectionSetup and/or RRCConnectionResume message, which may be referred to as RA Msg4, at step 1608, for example, after or in response to receiving the RRCConnectionRequest and/or RRCConnectionResumeRequest message. The wireless device 1620 may send to the base station 1621 an RRCConnectionSetupComplete and/or RRCConnectionResumeComplete message, which may be referred to as RA Msg5, at step 1609, for example, after or in response to receiving the RRCConnectionSetup and/or RRCConnectionResume. An RRC connection may be established between the wireless device 1620 and the base station 1621, and the random access procedure may end, for example, after or in response to receiving the RRCConnectionSetupComplete and/or RRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may be determined based on a channel state information reference signal (CSI-RS). A wireless device may use a CSI-RS in a multi-beam system for estimating the beam quality of the links between the wireless device and a base station. For example, based on a measurement of a CSI-RS, a wireless device may report CSI for downlink channel adaption. A CSI parameter may include a precoding matrix index (PMI), a channel quality index (CQI) value, and/or a rank indicator (RI). A wireless device may report a beam index based on a reference signal received power (RSRP) measurement on a CSI-RS. The wireless device may report the beam index in a CSI resource indication (CRI) for downlink beam selection. A base station may transmit a CSI-RS via a CSI-RS resource, such as via one or more antenna ports, or via one or more time and/or frequency radio resources. A beam may be associated with a CSI-RS. A CSI-RS may comprise an indication of a beam direction. Each of a plurality of beams may be associated with one of a plurality of CSI-RSs. A CSI-RS resource may be configured in a cell-specific way, for example, via common RRC signaling. Additionally or alternatively, a CSI-RS resource may be configured in a wireless device-specific way, for example, via dedicated RRC signaling and/or layer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices in or served by a cell may measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices in or served by a cell may measure a wireless device-specific CSI-RS resource. A base station may transmit a CSI-RS resource periodically, using aperiodic transmission, or using a multi-shot or semi-persistent transmission. In a periodic transmission, a base station may transmit the configured CSI-RS resource using a configured periodicity in the time domain. In an aperiodic transmission, a base station may transmit the configured CSI-RS resource in a dedicated time slot. In a multi-shot or semi-persistent transmission, a base station may transmit the configured CSI-RS resource in a configured period. A base station may configure different CSI-RS resources in different terms for different purposes. Different terms may include, for example, cell-specific, device-specific, periodic, aperiodic, multi-shot, or other terms. Different purposes may include, for example, beam management, CQI reporting, or other purposes.

FIG. 17 shows an example of transmitting CSI-RSs periodically for a beam. A base station 1701 may transmit a beam in a predefined order in the time domain, such as during time periods 1703. Beams used for a CSI-RS transmission, such as for CSI-RS 1704 in transmissions 1702C and/or 1703E, may have a different beam width relative to a beam width for SS-blocks transmission, such as for SS blocks 1702A, 1702B, 1702D, and 1702F-1702H. Additionally or alternatively, a beam width of a beam used for a CSI-RS transmission may have the same value as a beam width for an SS block. Some or all of one or more CSI-RSs may be included in one or more beams. An SS block may occupy a number of OFDM symbols (e.g., 4), and a number of subcarriers (e.g., 240), carrying a synchronization sequence signal. The synchronization sequence signal may identify a cell.

FIG. 18 shows an example of a CSI-RS that may be mapped in time and frequency domains. Each square shown in FIG. 18 may represent a resource block within a bandwidth of a cell. Each resource block may comprise a number of subcarriers. A cell may have a bandwidth comprising a number of resource blocks. A base station (e.g., a gNB in NR) may transmit one or more Radio Resource Control (RRC) messages comprising CSI-RS resource configuration parameters for one or more CSI-RS. One or more of the following parameters may be configured by higher layer signaling for each CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and RE locations in a subframe), CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, CDM type parameter, frequency density, transmission comb, QCL parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resource parameters.

CSI-RS may be configured using common parameters, for example, when a plurality of wireless devices receive the same CSI-RS signal. CSI-RS may be configured using wireless device dedicated parameters, for example, when a CSI-RS is configured for a specific wireless device. CSI-RSs may be included in RRC signaling. A wireless device may be configured, for example, depending on different MIMO beamforming types (e.g., CLASS A or CLASS B), with one or more CSI-RS resource configurations per each CSI process. As an example, a wireless device may be configured using at least one of the RRC signaling shown in FIGS. 19A to 19B.

CSI-RS resources may be activated or deactivated (e.g., for some types of MIMO beamforming) by using MAC signaling. A device (e.g., a base station) communicating in a network may activate and/or deactivate configured CSI-RS resources of a serving cell by sending an activation/deactivation CSI-RS resources MAC control element. The configured CSI-RS resources may be initially deactivated, for example, during configuration and/or after a handover.

FIG. 20A shows an example of an activation/deactivation CSI-RS resources MAC control element. The activation/deactivation CSI-RS resources MAC control element may be identified by a MAC subheader with LCID. The activation/deactivation CSI-RS resources MAC control element may have a variable size that may be based on the number of CSI processes configured with csi-RS-NZP-Activation by RRC (N). The N number of octets, shown in FIG. 20A, each of which may comprise a number of A fields (e.g., A1 to Ai, described below), may be included in ascending order of a CSI process ID, such as the CSI-ProcessId.

FIG. 20B shows an example of an activation/deactivation CSI-RS command that may activate and/or deactivate CSI-RS resources for a CSI process. For example, for a wireless device that is configured with transmission mode 9, N equals 1. Transmission mode 9 may be a transmission mode in which a base station may transmit data packets with up to 8 layers, for example, if configured with multiple antennas. A wireless device may receive the data packets based on multiple DMRSs (e.g., up to 8 DMRSs (or DMRS ports)). The activation/deactivation CSI-RS resources MAC control element may apply to the serving cell on which the wireless device may receive the activation/deactivation of CSI-RS resources MAC control element.

Activation/deactivation CSI-RS resources MAC control elements may comprise an octet of fields, shown as fields A1 to A8, that may indicate the activation/deactivation status of the CSI-RS resources configured by upper layers for the CSI process. A1 may correspond to the first entry in a list of CSI-RS, which may be specified by csi-RS-ConfigNZP-ApList configured by upper layers. A2 may correspond to the second entry in the list of CSI-RS, and each of A3 through A8 may correspond to the third through eighth entry, respectively, in the list of CSI-RS. The Ai field may be set to “1” to indicate that the i^(th) entry in the list of CSI-RS, which may be specified by csi-RS-ConfigNZP-ApList, shall be activated. The Ai field may be set to “0” to indicate that the i^(th) entry in the list shall be deactivated. For each CSI process, the number of Ai fields (e.g., i=1, 2, . . . , 8) which are set to “1” may be equal to the value of a higher-layer parameter, such as activatedResources.

A wireless device may be triggered with aperiodic CSI reporting, for example, after receiving a RRC for CSI-RS configuration and a MAC layer signaling for CSI-RS activation. The aperiodic CSI reporting may be associated with the CSI-RS resources indicated in a DCI, for example, with DCI format 0C. A CSI request field in DCI format 0C may indicate for which CSI process and/or CSI-RS resource the CSI reporting is configured, such as shown in Table 1 below.

TABLE 1 CSI Request field for PDCCH/EPDCCH with uplink DCI format in wireless device specific search space Value of CSI request field Description 000 No aperiodic CSI report is triggered 001 Aperiodic CSI report is triggered for a 1^(st) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 010 Aperiodic CSI report is triggered for a 2^(nd) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 011 Aperiodic CSI report is triggered for a 3^(rd) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 100 Aperiodic CSI report is triggered for a 4^(th) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 101 Aperiodic CSI report is triggered for a 5^(th) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 110 Aperiodic CSI report is triggered for a 6^(th) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c) 111 Aperiodic CSI report is triggered for a 7^(th) set of {CSI process, CSI-RS resource} configured by higher layers for serving cell_(c)

FIG. 18 shows three beams that may be configured for a wireless device, for example, in a wireless device-specific configuration. Any number of additional beams (e.g., represented by the column of blank squares) or fewer beams may be included. Beam 1 may be allocated with CSI-RS 1 that may be transmitted in some subcarriers in a resource block (RB) of a first symbol. Beam 2 may be allocated with CSI-RS 2 that may be transmitted in some subcarriers in a RB of a second symbol. Beam 3 may be allocated with CSI-RS 3 that may be transmitted in some subcarriers in a RB of a third symbol. All subcarriers in a RB may not necessarily be used for transmitting a particular CSI-RS (e.g., CSI-RS1) on an associated beam (e.g., beam 1) for that CSI-RS. By using frequency division multiplexing (FDM), other subcarriers, not used for beam 1 for the wireless device in the same RB, may be used for other CSI-RS transmissions associated with a different beam for other wireless devices. Additionally or alternatively, by using time domain multiplexing (TDM), beams used for a wireless device may be configured such that different beams (e.g., beam 1, beam 2, and beam 3) for the wireless device may be transmitted using some symbols different from beams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beam management procedure, a wireless device may monitor a channel quality of a beam pair link comprising a transmitting beam by a base station (e.g., a gNB in NR) and a receiving beam by the wireless device (e.g., a UE). When multiple CSI-RSs associated with multiple beams are configured, a wireless device may monitor multiple beam pair links between the base station and the wireless device.

A wireless device may transmit one or more beam management reports to a base station. A beam management report may indicate one or more beam pair quality parameters, comprising, for example, one or more beam identifications, RSRP, PMI, CQI, and/or RI, of a subset of configured beams.

A base station and/or a wireless device may perform a downlink L1/L2 beam management procedure. One or more downlink L1/L2 beam management procedures may be performed within one or multiple transmission and receiving points (TRPs), such as shown in FIG. 22 and FIG. 23, respectively.

FIG. 21 shows examples of three beam management procedures, P1, P2, and P3. Procedure P1 may be used to enable a wireless device measurement on different transmit (Tx) beams of a TRP (or multiple TRPs), for example, to support a selection of Tx beams and/or wireless device receive (Rx) beam(s) (shown as shaded ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP (or multiple TRPs) may include, for example, an intra-TRP and/or inter-TRP Tx beam sweep from a set of different beams (shown, in the top rows of P1 and P2, as unshaded ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Beamforming at a wireless device 2101, may include, for example, a wireless device Rx beam sweep from a set of different beams (shown, in the bottom rows of P1 and P3, as unshaded ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a wireless device measurement on different Tx beams of a TRP (or multiple TRPs) (shown, in the top row of P2, as unshaded ovals rotated in a counter-clockwise direction indicated by the dashed arrow), for example, which may change inter-TRP and/or intra-TRP Tx beam(s). Procedure P2 may be performed, for example, on a smaller set of beams for beam refinement than in procedure P1. P2 may be a particular example of P1. Procedure P3 may be used to enable a wireless device measurement on the same Tx beam (shown as shaded oval in P3), for example, to change a wireless device Rx beam if the wireless device 2101 uses beamforming.

Based on a wireless device's beam management report, a base station may transmit, to the wireless device, a signal indicating that one or more beam pair links are the one or more serving beams. The base station may transmit PDCCH and/or PDSCH for the wireless device using the one or more serving beams.

A wireless device 2101 (e.g., a UE) and/or a base station 2102 (e.g., a gNB) may trigger a beam failure recovery mechanism. The wireless device 2101 may trigger a beam failure recovery (BFR) request transmission, for example, if a beam failure event occurs. A beam failure event may include, for example, a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory. A determination of an unsatisfactory quality of beam pair link(s) of an associated channel may be based on the quality falling below a threshold and/or an expiration of a timer.

The wireless device 2101 may measure a quality of beam pair link(s) using one or more reference signals (RS). One or more SS blocks, one or more CSI-RS resources, and/or one or more demodulation reference signals (DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beam pair link. Each of the one or more CSI-RS resources may be associated with a CSI-RS resource index (CRI). A quality of a beam pair link may be based on one or more of an RSRP value, reference signal received quality (RSRQ) value, and/or CSI value measured on RS resources. The base station 2102 may indicate that an RS resource, for example, that may be used for measuring a beam pair link quality, is quasi-co-located (QCLed) with one or more DM-RSs of a control channel. The RS resource and the DM-RSs of the control channel may be QCLed when the channel characteristics from a transmission via an RS to the wireless device 2101, and the channel characteristics from a transmission via a control channel to the wireless device, are similar or the same under a configured criterion.

FIG. 22 shows an example of a beam failure event involving a single TRP. A single TRP such as at a base station 2201 may transmit, to a wireless device 2202, a first beam 2203 and a second beam 2204. A beam failure event may occur if, for example, a serving beam, such as the second beam 2204, is blocked by a moving vehicle 2205 or other obstruction (e.g., building, tree, land, or any object) and configured beams (e.g., the first beam 2203 and the second beam 2204), including the serving beam, are received from the single TRP. The wireless device 2202 may trigger a mechanism to recover from beam failure when a beam failure occurs.

FIG. 23 shows an example of a beam failure event involving multiple TRPs. Multiple TRPs, such as at a first base station 2301 and at a second base station 2306, may transmit, to a wireless device 2302, a first beam 2303 (e.g., from the first base station 2301) and a second beam 2304 (e.g., from the second base station 2306). A beam failure event may occur when, for example, a serving beam, such as the second beam 2304, is blocked by a moving vehicle 2305 or other obstruction (e.g., building, tree, land, or any object) and configured beams (e.g., the first beam 2303 and the second beam 2304) are received from multiple TRPs. The wireless device 2302 may trigger a mechanism to recover from beam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH (NR-PDCCH), on M beam pair links simultaneously, where M≥1 and the maximum value of M may depend at least on the wireless device capability. Such monitoring may increase robustness against beam pair link blocking. A base station may transmit, and the wireless device may receive, one or more messages configured to cause the wireless device to monitor NR-PDCCH on different beam pair link(s) and/or in different NR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC control element (MAC CE), that may comprise parameters related to a wireless device Rx beam setting for monitoring NR-PDCCH on multiple beam pair links. A base station may transmit one or more indications of a spatial QCL assumption between a first DL RS antenna port(s) and a second DL RS antenna port(s). The first DL RS antenna port(s) may be for one or more of a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH with DM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RS antenna port(s) may be for demodulation of a DL control channel. Signaling for a beam indication for a NR-PDCCH (e.g., configuration to monitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCI signaling, or specification-transparent and/or an implicit method, and any combination thereof.

For reception of unicast DL data channel, a base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of DL data channel. A base station may transmit DCI (e.g., downlink grants) comprising information indicating the RS antenna port(s). The information may indicate the RS antenna port(s) which may be QCLed with DM-RS antenna port(s). A different set of DM-RS antenna port(s) for the DL data channel may be indicated as a QCL with a different set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parameters between CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSs QCLed with DM-RS for a PDCCH to monitor beam pair link quality. If a beam failure event occurs, the wireless device may transmit a beam failure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, for example, via an uplink physical channel or signal, a base station may detect that there is a beam failure event, for the wireless device, by monitoring the uplink physical channel or signal. The base station may initiate a beam recovery mechanism to recover the beam pair link for transmitting PDCCH between the base station and the wireless device. The base station may transmit one or more control signals, to the wireless device, for example, after or in response to receiving the beam failure recovery request. A beam recovery mechanism may be, for example, an L1 scheme, or a higher layer scheme.

A base station may transmit one or more messages comprising, for example, configuration parameters of an uplink physical channel and/or a signal for transmitting a beam failure recovery request. The uplink physical channel and/or signal may be based on at least one of the following: a non-contention based PRACH (e.g., a beam failure recovery PRACH or BFR-PRACH), which may use a resource orthogonal to resources of other PRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH or BFR-PUCCH); and/or a contention-based PRACH resource. Combinations of these candidate signal and/or channels may be configured by a base station.

In wireless communications, various beam procedures may be performed, such as downlink beam management, downlink beam failure recovery, and uplink beam management. Each beam procedure may have an associated DCI format, examples of which are described below regarding Table 8. A base station may transmit different DCIs with different DCI formats to complete different beam procedures. A base station may transmit a first DCI with a first DCI format to complete beam failure recovery procedure. The first DCI may comprise beam information of a candidate beam. A base station may transmit a second DCI with a second DCI format to complete uplink beam management. The second DCI may comprise beam information of an SRS. A base station may transmit a third DCI with a third DCI format to complete downlink beam management. The third DCI may comprise beam information of a serving beam of the base station. A wireless device may monitor a physical downlink control channel (PDCCH) and the wireless device may perform one or more blind decoding attempts before ultimately determining a type of beam procedure to perform. The wireless device may determine a type of beam procedure in a more efficient and timely manner, for example, by receiving, from a base station, an indication of the type of beam procedure to perform in one or more messages comprising downlink control information (DCI). Some procedures may be unified to comprise the same DCI format. By using the same DCI format for different types of procedures, a wireless device may reduce power usage and/or increase power efficiency, for example, by reducing blind decoding attempts, of the DCI, that may be associated with PDCCH monitoring. A beam type parameter indication field may be used to indicate a particular procedure, for example, that may comprise a DCI format in common with one or more other procedures. A downlink beam failure recovery procedure and an uplink beam management may be associated with the same DCI format (e.g., a unified DCI), and each procedure may be indicated by a different beam type parameter value (e.g., binary 0 or 1). Additionally or alternatively, each of downlink beam management, downlink beam failure recovery, and uplink beam management may be associated with the same DCI format (e.g., a unified DCI), and each procedure may be indicated by a respective beam type parameter value (e.g., binary 01, 10, or 10). By using the same DCI format for different types of procedures, of which may be identified by a beam type parameter, more types of procedures may be used, including, for example, more procedures that may be developed in the future, with the same DCI format.

A base station may determine a type of beam procedure for a wireless device to perform. The base station may transmit, and the wireless device may receive, at least one radio resource control (RRC) message. The at least one RRC message may comprise one or more first parameters for a downlink beam failure recovery procedure; and one or more second parameters for an uplink beam management procedure. Additionally or alternatively, the at least one RRC message may comprise one or more third parameters for a downlink beam management procedure, or a fourth or more parameters for one or more additional procedures. The one or more first parameters of the downlink beam failure recovery procedure, and/or the one or more third parameters of the downlink beam management procedure, may comprise one or more of: reference signal (RS) resource parameters of a first plurality of reference signals (RSs); RS resource parameters of a second plurality of RSs; or one or more random access channel resources. The one or more second parameters of the uplink beam management procedure may comprise one or more of: a bandwidth of a sounding reference signal (SRS); a numerology of the SRS; a frequency of the SRS; or a time resource of the SRS. The base station may transmit, and the wireless device may receive, via a downlink control channel, downlink control information (DCI). The DCI may comprise one or more beam information fields, and an indication field indicating that the one or more beam information fields comprises: one or more beam parameters for the downlink beam failure recovery procedure; or one or more beam parameters for the uplink beam management procedure. Additionally or alternatively, the indication field may indicate that the one or more beam information fields comprises one or more beam parameters for the downlink beam management procedure. The wireless device may adjust, based on the indication field, one or more transceiver parameters. The one or more transceiver parameters may comprise at least one of: a receiving beamforming precoder (e.g., amplitude, or phase); and/or a transmission beamforming precoder (e.g., amplitude, or phase). The wireless device may adjust the one or more transceiver parameters by adjusting beams for receiving (e.g., receiving beams or Rx beams) based on the one or more beam information fields of the DCI, for example, if the indication field of the DCI indicates that the one or more beam information fields comprises one or more beam parameters of the downlink beam failure recovery procedure. The wireless device may adjust the one or more transceiver parameters by adjusting beams for transmitting (e.g., transmitting beams or Tx beams) based on the one or more beam information fields of the DCI, for example, if the indication field of the DCI indicates that the one or more beam information fields comprises one or more beam parameters of the uplink beam management procedure.

The wireless device may initiate, for example, after or in response to detecting at least one beam failure based on the one or more first parameters, the downlink beam failure recovery procedure. The wireless device may initiate, based on the one or more second parameters, the uplink beam management procedure. The wireless device may initiate, based on the one or more third parameters, the downlink beam management procedure. The wireless device may initiate, based on receiving a second DCI indicating a transmission of at least one sounding reference signal, the uplink beam management procedure. The uplink beam management procedure may comprise transmitting, by the wireless device, at least one sounding reference signal (SRS) based on the one or more second parameters. The wireless device may determine, based on the indication field indicating that the one or more beam information fields comprises one or more beam parameters for the uplink beam management procedure, that the DCI comprises one or more SRS resource indexes. The wireless device may determine, based on the indication field indicating that the one or more beam information fields comprises one or more beam parameters for the downlink beam failure recovery procedure, that the DCI comprises one or more channel state information reference signal (CSI-RS) resource indexes.

The base station may transmit, and the wireless device may receive, at least one RRC message comprising one or more parameters for: a downlink beam failure recovery procedure; and/or an uplink beam management procedure. Additionally or alternatively, the at least one RRC message may comprise one or more parameters for a downlink beam management procedure. The base station may transmit, and the wireless device may receive, via a downlink control channel, a DCI comprising: one or more beam information fields; and a beam procedure type field. The beam procedure type field may associate the one or more beam information fields with: the downlink beam failure recovery procedure; the downlink beam management procedure; and/or the uplink beam management procedure. The base station may determine, based on the beam procedure type field associating the one or more beam information fields with the uplink beam management procedure, one or more SRS resource indexes for the DCI. If the base station receives, from the wireless device, multiple SRSs for uplink beam management, the base station may select one SRS from the multiple SRS as a best uplink beam. The base station may send, to the wireless device, a DCI comprising the best SRS and/or an SRS resource index. The base station may determine, based on the beam procedure type field associating the one or more beam information fields with the downlink beam failure recovery procedure, one or more channel state information reference signal (CSI-RS) resource indexes for the DCI. The wireless device, and/or the base station, may perform, based on the beam procedure type field, either a downlink beam failure recovery procedure, a downlink beam management procedure, or an uplink beam management procedure.

The wireless device may transmit one or more SRSs. The base station may send an indication for the wireless device to transmit one or more SRSs for channel quality estimation, which may be to enable frequency-selective scheduling on the uplink. Additionally or alternatively, transmission of SRS may be used for other purposes, such as to enhance power control, and/or to support various startup functions for wireless devices not recently scheduled. Such startup functions may include, for example, initial modulation and coding scheme (MCS) selection, initial power control for data transmissions, timing advance, and/or frequency semi-selective scheduling.

Subframes in which SRSs may be transmitted by any wireless device within a cell may be indicated by cell-specific broadcast signaling, and/or by wireless device-specific signaling. For common configured SRS transmission, the subframes for SRS transmission may be indicated by a 4-bit cell-specific parameter, such as srsSubframeConfiguration, indicating up to 15 possible sets of subframes in which SRS may be transmitted within each radio frame, shown as in Table 2 below.

TABLE 2 Frame structure type 1 sounding reference signal subframe configuration Configuration Period Transmission offset srs-SubframeConfig Binary T_(SFC) (subframes) Δ_(SFC) (subframes) 0 0000 1 {0} 1 0001 2 {0} 2 0010 2 {1} 3 0011 5 {0} 4 0100 5 {1} 5 0101 5 {2} 6 0110 5 {3} 7 0111 5 {0, 1} 8 1000 5 {2, 3} 9 1001 10 {0} 10 1010 10 {1} 11 1011 10 {2} 12 1100 10 {3} 13 1101 10 {0, 1, 2, 3, 4, 6, 8} 14 1110 10 {0, 1, 2, 3, 4, 5, 6, 8} 15 1111 reserved reserved

A wireless device may receive an indication to transmit at least one of two types of SRS: periodic SRS transmission (e.g., type 0) and/or aperiodic SRS transmission (e.g., type 1). Periodic SRS transmission from a wireless device may occur at regular time intervals, for example, from as often as each 2 ms to as infrequently as each 160 ms. The SRS transmission may be in the last several SC-FDMA or OFDM symbols in the configured subframes, such as shown in FIG. 24.

FIG. 24 shows an example arrangement of subframes that may comprise SRS transmissions. Each rectangle at the top row of FIG. 24 may correspond to one subframe. An SRS period may comprise a plurality of subframes, such as N subframes. Each subframe may comprise a plurality of symbols, such as shown at the bottom row of FIG. 24. One or more symbols may comprise an SRS transmission. An SRS transmission may be included in each SRS period.

A base station (e.g., a gNB) may transmit, to a wireless device, a DCI. The base station may transmit the DCI via a PDCCH, for example, as part of a scheduling grant, which may trigger an aperiodic SRS transmission, for example, a one-shot transmission. The time instants for periodic and aperiodic SRS may be configured per device using high layer signaling. For example, for wireless device-specific periodic SRS configuration, the subframes used for SRS transmission may be indicated by a wireless device-specific RRC signaling, for example, using a parameter such as a 10-bit srs-ConfigIndex, as shown in Table 3 below.

TABLE 3 UE Specific SRS Periodicity T_(SRS) and Subframe Offset Configuration T_(offset) for trigger type 0, FDD SRS SRS Configuration Subframe Index I_(SRS) SRS Periodicity T_(SRS) (ms) Offset T_(offset) 0-1 2 I_(SRS) 2-6 5 I_(SRS)-2  7-16 10 I_(SRS)-7 17-36 20 I_(SRS)-17 37-76 40 I_(SRS)-37  77-156 80 I_(SRS)-77 157-316 160 I_(SRS)-157 317-636 320 I_(SRS)-317  637-1023 reserved reserved

For aperiodic SRS transmission, the subframes for SRS transmission may be indicated by a parameter, such as a 5-bit srs-configIndex, as shown in Table 4 below.

TABLE 4 UE Specific SRS Periodicity T_(SRS,1) and Subframe Offset Configuration T_(offset,1) for trigger type 1, FDD SRS Configuration Index SRS Periodicity SRS Subframe I_(SRS) T_(SRS,1) (ms) Offset T_(offset,1) 0-1 2 I_(SRS) 2-6 5 I_(SRS)-2  7-16 10  I_(SRS)-7 17-31 reserved reserved

A wireless device may be configured, via high layer signaling, with frequency related parameters for SRS transmission (e.g., bandwidth, frequency hopping, transmission comb and offset, and frequency-domain position). FIG. 25 shows an example of high layer signaling for SRS parameter configuration.

A base station (e.g., a gNB) may transmit, to a wireless device, RRC signaling to configure multiple sets of SRS parameters, for example, for aperiodic SRS transmission with type 1 triggering. The RRC signaling may comprise a DCI with a 2-bit SRS request for the wireless device. The 2-bit SRS request may indicate an SRS parameter set, such as shown below in Tables 5, 6 and 7, for different DCI formats.

TABLE 5 SRS request value for trigger type 1 in DCI format 4/4A/4B Value of SRS request field Description 00 No type 1 SRS trigger 01 The 1^(st) SRS parameter set configured by higher layers 10 The 2^(nd) SRS parameter set configured by higher layers 11 The 3^(rd) SRS parameter set configured by higher layers

TABLE 6 SRS request value for trigger type 1 in DCI format 0B Value of SRS request field Description 00 No type 1 SRS trigger 01 Type 1 SRS trigger and first scheduled PUSCH subframe 10 Type 1 SRS trigger and second scheduled PUSCH subframe 11 Type 1 SRS trigger and last scheduled PUSCH subframe

TABLE 7 SRS request value for trigger type 1 in DCI format 3B and for UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission Value of SRS request field Description 00 No type 1 SRS trigger for a 1^(st) set of serving cells configured by higher layers 01 Type 1 SRS trigger for a 2^(nd) set of serving cells configured by higher layers 10 Type 1 SRS trigger for a 3^(rd) set of serving cells configured by higher layers 11 Type 1 SRS trigger for a 4^(th) set of serving cells configured by higher layers

A wireless device may transmit SRS precoded with same or different Tx beams within a time duration. The wireless device may determine a Tx beam for SRS transmission, based on one or more of: applying gNB-transparent Tx beam to an SRS (e.g., the wireless device may determine a Tx beam for each SRS port/resource), or a base station indication (e.g., via SRI).

A wireless device may transmit SRSs, with a number of SRS ports (e.g., 1, 2, or 4), comb levels (e.g., 2 or 4), and/or configurable frequency hopping, according to configuration parameters indicated by RRC signaling. A wireless device may transmit SRSs using one or more configured SRS parameters. The one or more configured SRS parameters may comprise one or more of: a configurable SRS bandwidth, SRS numerologies, density in frequency domain (e.g., comb levels) and/or in time domain (including, for example, multi-symbol SRS transmissions), partial band size, and/or full band size.

A base station (e.g., a gNB) may transmit to a wireless device one or more RRC messages comprising one or more SRS configurations. At least one of the one or more SRS configurations may comprise one or more SRS resources. At least one of the one or more SRS resources may comprise a SRS resource index (SRI), a set of resource elements (RE) within a time duration and/or frequency span, and N antenna ports (e.g., where N≥1). At least one of the one or more SRS resources may be used for aperiodic transmission. A wireless device may transmit one or more SRSs by using sequences that may provide low peak-to-average power ratio (e.g., Zadoff-Chu sequences).

A wireless device may be equipped with multiple Tx antennas, which may enable multiple uplink Tx beam transmissions. The wireless device may perform uplink beam management by configuration, for example, if there is no reciprocity between downlink beamforming and uplink beamforming.

FIG. 26 shows an example for three types of uplink beam management that may be supported by a wireless device 2601. The uplink beam management procedures for Tx/Rx beams shown in FIG. 26 may be similar to the downlink beam management procedures for TX/Rx beams described above regarding FIG. 21. A base station 2602 (e.g., a gNB) and the wireless device 2601 may perform a first type (e.g., U1) of uplink beam management procedure, for example, to select a suitable beam pair link (shown as shaded ovals in U1) between a Tx beam of the wireless device 2601 (shown in the bottom row of U1 as unshaded ovals rotated in a clockwise direction indicated by the dashed arrow) and a Rx beam of the base station 2602 (shown in the top row of U1 as unshaded ovals rotated in a counter-clockwise direction indicated by the dashed arrow). This first type of uplink beam management procedure may comprise beam sweeping by the wireless device and/or beam sweeping by the base station 2602. The base station 2602 may perform a second type (e.g., U2) of uplink beam management procedure, for example, to change a Rx beam such as by performing a Rx beam sweeping (shown in the top row of U2 as unshaded ovals rotated in a counter-clockwise direction indicated by the dashed arrow). During this second type of uplink beam procedure, the base station 2602 may assume that the Tx beam direction of the wireless device 2601 is fixed (shown as the shaded oval in the bottom row of U2). The wireless device 2601 may perform a third type (e.g., U3) of uplink beam management procedure, for example, to change a Tx beam such as by performing a Tx beam sweeping (shown in the bottom row of U3 as unshaded ovals rotated in a clockwise direction indicated by the dashed arrow). During this third type of uplink beam management procedure, the base station 2602 may indicate the best Tx beam (shown as the shaded ovals in the top row of U3) to the wireless device 2601.

The wireless device 2601 may perform random access procedure on multiple Tx beams, for example, in the first procedure U1. The base station 2602 may transmit a RAR on a Tx beam, for example, in the first procedure U1, and the RAR may include the information of the best determined Tx beam the wireless device may use.

The base station 2602 may transmit, for example, in the second procedure U2, an indication to the wireless device 2601 to keep a Tx beam unchanged for a configured time, during which, the base station 2602 may perform Rx beam sweeping to find out the best determined Rx beam. The wireless device 2601 may not necessarily know which Rx beam the base station 2602 may finally select.

The base station 2602 may transmit, for example, to the wireless device 2601 in the third procedure U3, a DCI that may trigger uplink transmit beam sweeping by the wireless device 2601 in a configured time, during which, the base station 2602 may keep the Rx beam unchanged. The base station 2602 may measure the channel of the beam pair link. The base station 2602 may indicate to the wireless device 2601 a best determined Tx beam. The wireless device 2601 may use the best determined Tx beam for future uplink transmission, for example, if the Tx beam satisfies a selection criteria.

The base station 2602 may use beam selection based on measurement of one or more uplink reference signals (e.g., SRSs). The base station 2602 may transmit one or more messages comprising one or more SRS configurations. The one or more SRS configurations may comprise one or more of: SRS resource index (SRI), SRS time parameters (e.g., subframe, offset, symbols, and/or duration), frequency parameters (e.g., SRS bandwidth, frequency position, hopping bandwidth, comb factors), cyclic shift parameter, and/or beam sweeping parameters (e.g., beam sweeping duration, beam rotating or beam kept fixed). The base station 2602 may transmit control information (e.g., one or more DCI or SRS resources) that may trigger an uplink beam sweeping. The control information may comprise at least one or more SRS resources. The wireless device 2601 may transmit one or more SRSs using the SRS parameters configured by an RRC message and/or indicated by a DCI. The base station 2602 may select the Tx beam using a selection criteria (e.g., the best RSRP of received SRS). The base station 2602 may indicate, to the wireless device 2601 via one or more DCI, the SRI associated with the selected Tx beam.

An uplink beam failure event may occur, for example, in the third procedure U3, if the wireless device 2601 fails to receive a DCI indicating the best Tx beam. An uplink beam failure may be recovered using an L1 or higher layer mechanism.

The base station 2602 may transmit, via a PDCCH, a DCI for scheduling decision and power-control commands. The DCI may comprise one or more of: downlink scheduling assignments, uplink scheduling grants, or power-control commands. The downlink scheduling assignments may comprise one or more of: PDSCH resource indication, transport format, HARQ information, control information related to multiple antenna schemes, or a command for power control of the PUCCH used for transmission of ACK/NACK based on or in response to downlink scheduling assignments. The uplink scheduling grants may comprise one or more of: PUSCH resource indication, transport format, HARQ related information, or a power control command of the PUSCH.

Different types of control information may correspond to different DCI message sizes. Supporting spatial multiplexing with noncontiguous allocation of RBs in the frequency domain may require a larger scheduling message in comparison with an uplink grant that may allow only frequency-contiguous allocation. The DCI may be categorized into different DCI formats, where a format may correspond to a certain message size and/or usage. Table 8 below provides a summary of example DCI formats, including the size for an example of a 20 MHz FDD operation with two Tx antennas at the base station 2602 and no carrier aggregation.

The wireless device 2601 may monitor one or more PDCCH to detect one or more DCI with one or more DCI formats. The one or more PDCCH may be transmitted in common search space or wireless device-specific search space. The wireless device 2601 may monitor PDCCH with only a limited set of DCI format, for example, to save power consumption. The wireless device 2601 may not be required to detect a DCI with DCI format 6, which may be used for an eMTC wireless device. The wireless device 2601 may consume more power based on the number of DCI formats to be detected. The more DCI formats to be detected, the more power may be consumed by the wireless device 2601.

TABLE 8 example DCI format and usage DCI Example format size (Bits) Usage Uplink 0 45 Uplink scheduling grant 4 53 Uplink scheduling grant with spatial multiplexing 6-0A, 6-0B 46, 36 Uplink scheduling grant for eMTC devices Downlink 1C 31 Special purpose compact assignment 1A 45 Contiguous allocation only 1B 46 Codebook-based beamforming using CRS 1D 46 MU-MIMO using CRS 1 55 Flexible allocations 2A 64 Open-loop spatial multiplexing using CRS 2B 64 Dual-layer transmission using DM-RS (TM 8) 2C 66 Multi-layer transmission using DM-RS (TM9) 2D 68 Multi-layer transmission using DM-RS (TM9) 2 67 Closed-loop spatial multiplexing using CRS 6-1A, 6-1B 46, 36 Downlink scheduling grants for eMTC devices Special 3, 3A 45 Power control commands 5 Sidelink operation 6-2 Paging/direct indication for eMTC devices

Information in the DCI formats that may be used for downlink scheduling may be organized into different groups. One or more fields of the DCI formats may comprise one or more of: resource information, such as a carrier indicator (e.g., 0 or 3 bits) and/or a RB allocation; a HARQ process number; an MCS, new data indicator (NDI), and/or RV (e.g., for the first TB and/or for the second TB); MIMO related information such as PMI, precoding information, a transport block swap flag, a power offset between PDSCH and a reference signal, a reference-signal scrambling sequence, a number of layers, and/or a number of antenna ports for a transmission; PDSCH resource-element mapping and/or QCI; downlink assignment index (DAI); a transmit power control (TPC) for PUCCH; a SRS request (e.g., 1 bit), that may comprise an indication of or trigger for a one-shot SRS transmission; an ACK and/or NACK offset; a DCI format indication, for example, which may be used to differentiate between DCI format 1A and DCI format 0 or other formats that may have the same message size; and/or padding (e.g., if necessary).

Information in the DCI formats that may be used for uplink scheduling may be organized into different groups. One or more fields of the DCI formats may comprise one or more of: resource information, such as a carrier indicator, resource allocation type, and/or a RB allocation; an MCS and/or NDI (e.g., for the first TB and/or for the second TB); a phase rotation of the uplink demodulation reference signal (DMRS); precoding information; a CSI request, a request for an aperiodic CSI report; a SRS request (e.g., 2 bits), that may comprise an indication of or a trigger for an aperiodic SRS transmission that may use one of up to three preconfigured settings; an uplink index/DAI; a TPC for PUSCH; a DCI format indication, for example, which may be used to differentiate between DCI format 1A and DCI format 0; and/or padding (e.g., if necessary).

A base station may transmit one or more PDCCH in different control resource sets, for example, which may support wide bandwidth operation. The base station may transmit one or more RRC message comprising configuration parameters of one or more control resource sets. At least one of the one or more control resource sets may comprise one or more of: a first OFDM symbol (e.g., CORESET_StartSymbol); a number of consecutive OFDM symbols (e.g., CORESET_NumSymbol); a set of resource blocks (e.g., CORESET_RBSet); a CCE-to-REG mapping (e.g., CORESET_mapping); and/or a REG bundle size, such as for interleaved CCE-to-REG mapping (e.g., CORESET_REG_bundle).

The base station may transmit one or more messages comprising configuration parameters of one or more active bandwidth parts (BWPs). The one or more active BWPs may have different numerologies. The base station may transmit one or more control information for cross-BWP scheduling to a wireless device.

FIG. 27 shows an example for a downlink beam management procedure, such as a beam selection. The downlink beam management procedure may comprise procedure P2 described above regarding FIG. 21. The downlink beam management procedure may comprise transmitting by a base station 2702, and receiving by a wireless device 2701, a DCI for indicating or confirming one or more CSI-RSs, which may be based on or in response to beam reporting. The base station 2702 may transmit, to the wireless device 2701, one or more messages comprising at least one configuration parameters for a downlink beam management procedure (e.g., “DL BM config” in FIG. 27). The one or more messages may comprise one or more: RRC messages, MAC messages, and/or control information messages (e.g., DCI via one or more PDCCH, such as indicated by “DCI X” in FIG. 27). The one or more configuration parameters for the downlink beam management procedure may comprise one or more of: at least one RS type (e.g., SS block, CSI-RS, and/or DMRS of PBCH); a RS configuration, such as a CSI-RS resource configuration (e.g., CRI, CSI-R ports, time and/or frequency, and/or periodicity), for example, if a CSI-RS is configured for the downlink beam management procedure; QCL parameters (e.g., an indication indicating whether a RS resource is QCLed with a DMRS of a PDCCH); a measurement setting (e.g., a CSI measurement configuration, and/or an interference measurement configuration); a reporting setting, such as a reporting type (e.g., a CSI reporting type, beam management reporting type, or beam failure reporting type); a reporting quantity (e.g., RSRP, RSRQ, and/or CSI); a reporting timing (e.g., periodic, aperiodic, or wireless device-triggered); and/or a reporting triggering parameter (e.g., a timer, and/or one or more thresholds).

The wireless device 2701 may perform a downlink beam management based on parameters of one or more: RRC message, MAC message, and/or DCI. The downlink beam management procedure may comprise the following. The wireless device 2701 may perform a measurement on one or more downlink reference signals (e.g., “UE measurement,” which may be associated with the shaded oval in the “Beam selection” box, as shown in FIG. 27). The reference signals may be indicated by the one or more RRC message, MAC message, and/or DCI. The wireless device 2701 may transmit, to the base station 2702, one or more parameters indicating one or more reference signals. The wireless device 2701 may transmit the one or more parameters in a report that may indicate a beam quality. The wireless device 2701 may transmit, to the base station 2702, the one or more parameters with one or more measurement results (e.g., RSRP, RSRQ, and/or CSI) that may be associated with the one or more reference signals. The above wireless device transmission(s) may be indicated by “UE reporting” shown in FIG. 27. The wireless device 2701 may receive, from the base station 2702, one or more messages (e.g., “DCI Y” shown in FIG. 27) indicating one or more parameters associated with at least one of the one or more reference signals. The one or more messages (e.g., “DCI Y”) may be based on, and/or transmitted in response to, a transmission, by the wireless device 2701, of the one or more parameters indicating one or more reference signals (e.g., “UE reporting”).

FIG. 28 shows an example procedure for a beam failure recovery procedure, such as a downlink beam failure recovery. The beam failure recovery procedure may be used in the example of FIG. 22 and/or FIG. 23 described above. The beam failure recovery procedure may comprise transmitting, by a base station 2802, and receiving, by a wireless device 2801, a DCI for indicating or confirming one or more CSI-RSs, which may be based on or in response to a PRACH transmission (e.g., a beam failure recovery request). The base station 2802 (e.g., a gNB) may transmit, to the wireless device 2801, one or more messages comprising one or more configuration parameters for a downlink beam failure recovery procedure (e.g., “DL BM config” in FIG. 28). The one or more messages may comprise one or more: RRC messages, MAC messages, and/or control information messages (e.g., DCI via one or more PDCCH, such as indicated by “DCI X” in FIG. 28). The one or more configuration parameters of the downlink beam failure recovery procedure may comprise one or more of: at least one RS type (e.g., SS block, or CSI-RS, or DMRS of PBCH); a RS configuration (e.g., CSI-RS resource configuration); QCL parameters (e.g., an indication indicating whether a RS resource is QCLed with a DMRS of a PDCCH); beam failure recovery request channel configuration (e.g., PRACH preamble, time and/or frequency, hopping, and/or power control command); a measurement setting (e.g., CSI, RSRP, and/or RSRQ); a reporting setting, such as a reporting type (e.g., a CSI reporting type, beam management reporting type, or beam failure reporting type); a reporting quantity (e.g., RSRP, RSRQ, and/or CSI); a reporting timing (e.g., aperiodic, or wireless device-triggered); and/or a reporting trigger parameter (e.g., a timer, and/or one or more thresholds).

The wireless device 2801 may perform a downlink beam failure recovery procedure based on parameters of one or more: RRC message, MAC message, and/or DCI. The downlink beam failure recovery procedure may comprise the following. The wireless device 2801 may perform a measurement on one or more reference signals (e.g., “UE measurement” in FIG. 28). The wireless device 2801 may transmit, to the base station 2802, one or more preambles associated with one or more reference signals (e.g., for candidate beams). The wireless device 2801 may transmit, to the base station 2802, the one or more preambles if, or based on whether, one or more criteria of a beam failure event being satisfied. The above wireless device transmission(s), or another wireless device transmission, may be indicated by “BFR Request” shown in FIG. 28, which may comprise a beam failure recovery request. The wireless device 2801 may receive, from the base station 2802, one or more messages (e.g., “DCI Y” shown in FIG. 28) indicating one or more parameters associated with at least one of the one or more reference signals. The one or more messages (e.g., “DCI Y”) may be based on, and/or transmitted in response to, a transmission, by the wireless device 2801, of one or more preambles associated with one or more reference signals (e.g., “BFR request”).

The one or more criteria of a downlink beam failure event may comprise one or more of: measurement of one or more reference signal below a configured threshold associated with a configured timer; measurement of one or more reference signals below a configured threshold without a configured timer; and/or measurement of one or more reference signals above a configured threshold. Any of the above measurements may comprise one or more of a RSRP, RSRQ, and/or CQI.

FIG. 29 shows an example procedure for an uplink beam management procedure. The uplink beam management procedure may comprise procedure U3 described above regarding FIG. 26. The uplink beam management procedure may comprise transmitting, by a base station 2902, and receiving, by a wireless device 2801, a DCI for indicating or confirming one or more SRSs, which may be based on or in response to one or more SRS transmissions. The base station 2902 (e.g., a gNB) may transmit, to the wireless device 2901, one or more messages comprising one or more configuration parameters for an uplink beam management procedure (e.g., “UL BM config” in FIG. 29). The one or more messages may comprise one or more: RRC messages, MAC messages, and/or control information messages (e.g., DCI via one or more PDCCH, such as indicated by “DCI X” in FIG. 29). The one or more configuration parameters of the uplink beam management procedure may comprise one or more of: at least one uplink RS type (e.g., SRS, uplink DMRS, or PRACH); a RS configuration (e.g., one or multiple SRS resources, each of which may be associated with a SRI); QCL parameters (e.g., an indication indicating whether a SRS resource is QCLed with a DMRS of a PUCCH/PUSCH); and/or a SRS power control command.

The wireless device 2901 may perform an uplink beam management procedure based on parameters of one or more: RRC message, MAC message, and/or DCI. The uplink beam management procedure may comprise the following. The wireless device 2901 may perform Tx beam sweeping and the base station 2902 may perform beam measurement (e.g., “UE Tx beam sweeping and measurement” in FIG. 29). The wireless device 2901 may transmit, to the base station 2902, one or more uplink RSs (e.g., SRSs) with the parameters configured. The wireless device 2901 may receive, from the base station 2902, one or more messages (e.g., “DCI Y” shown in FIG. 29). The one or more messages (e.g., “DCI Y”) may indicate one or more parameters. The one or more parameters may indicate at least one of the one or more uplink RSs. The one or more messages (e.g., “DCI Y”) may be based on, and/or transmitted in response to, a transmission of the one or more uplink RSs (e.g., “UE TX beam sweeping and measurement” in FIG. 29).

FIG. 30 shows an example that may be performed by a base station, for example, for downlink beam management, downlink beam failure recovery, and/or uplink beam management. At step 3001, the base station may determine and/or send to a wireless device configuration parameters and/or control information. The base station may determine and/or send to a wireless device one or more messages comprising configuration parameters for one or more of: a downlink beam management procedure, a downlink beam failure recovery procedure, and/or an uplink beam management procedure. Additionally or alternatively, the base station may determine and/or send to a wireless device one or more control information that may indicate and/or command performing one or more of the downlink beam management procedure, the downlink beam failure recovery procedure, and/or the uplink beam management procedure.

At step 3002, the base station may determine one or more procedures to perform, which may comprise a downlink beam management procedure (shown in path “A”), an uplink beam management procedure (shown in path “B”), or a downlink beam failure recovery procedure (shown in path “C”). One or more beam procedures may be included, for example, depending on whether the beam procedure is associated with the same DCI format as another beam procedure. At least one of the above beam procedures may be excluded from FIG. 30, for example, the one or more beam procedures may comprise an uplink beam management procedure (shown in path “B”) and a downlink beam failure recovery procedure (shown in path “C”) but not a downlink beam management procedure (shown in path “A”). Another other combination of beam procedures may be performed. Additional beam procedures (not shown) may be included in addition to or in place of any of the beam procedures described with respect to FIG. 30.

At step 3003, if a determination is made to perform a downlink beam management procedure (path “A” from step 3002), the base station may send, to the wireless device, an indication of, or a command for, the downlink beam management procedure. The wireless device may send (e.g., after the wireless device receives the indication or command), to the base station, one or more beam reports. At step 3004, the base station may receive one or more beam reports. At step 3005, the base station may determine and/or set a beam parameter as an index associated with a serving beam, for example, after or in response to the base station receiving one or more beam report. The base station may determine and/or set a beam parameter of a DCI as an index of a synchronization signal block (SSB) or CSI-RS associated with a serving beam. Additionally or alternatively, at step 3005, the base station may determine and/or set an indicator as a first value indicating that the beam parameter is for downlink beam management. The base station may determine and/or set an indicator of a DCI as the first value. At step 3012, the base station may send the indicator, and/or one or more messages comprising the indicator, to the wireless device. The base station may transmit the DCI, which may comprise the indicator, via a downlink control channel. The base station may transmit one or more DCI via one or more PDCCH to the wireless device, which may be based on or in response to one or more of: a transmission by the wireless device of one or more beam reports via PUCCH and/or PUSCH for the downlink beam management procedure, a transmission by the wireless device of one or more beam information via PRACH for the downlink beam failure recovery procedure, or a transmission of one or more SRSs for the uplink beam management. The one or more DCI may comprise one or more: beam information fields; and an indication field indicating whether the one or more beam information fields comprise one or more beam parameters for the downlink beam management procedure, the downlink beam failure recovery procedure, or the uplink beam management procedure. One or more beam information fields may comprise one or more parameters indicating one or more: CSI-RS resources or SS blocks, for example, if the indication field in the one or more DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam management procedure.

At step 3006, if a determination is made to perform an uplink beam management procedure (path “B” from step 3002), the base station may send, to the wireless device, an indication of, or a command for, the uplink beam management procedure. The wireless device may send (e.g., after the wireless device receives the indication or command), to the base station, one or more sounding reference signals (SRSs). At step 3007, the base station may receive one or more SRSs. At step 3008, the base station may determine and/or set a beam parameter as an index of an SRS, for example, after or in response to the base station receives the SRS. The base station may determine and/or set a beam parameter of a DCI as an index of an SRS. Additionally or alternatively, at step 3008, the base station may determine and/or set an indicator as a second value indicating that the beam parameter is for uplink beam management. The base station may determine and/or set an indicator of a DCI as the second value. At step 3012, the base station may send the indicator, and/or one or more messages comprising the indicator, to the wireless device. The base station may transmit the DCI, which may comprise the indicator, via a downlink control channel. One or more beam information fields may comprise one or more parameters indicating one or more SRSs, for example, if the indication field in the one or more DCI indicates the one or more beam information fields comprise one or more beam parameters for the uplink beam management procedure.

At step 3009, if a determination is made to perform a downlink beam failure recovery procedure (path “C” from step 3002), the base station may monitor PRACH resources, for example, to determine whether a preamble for the BFR recovery procedure is received. The wireless device may send (e.g., after the wireless device detects one or more beam failures), to the base station, one or more preambles (e.g., BFR preambles). At step 3010, the base station may receive a preamble (e.g., a BFR preamble). At step 3011, the base station may determine and/or set a beam parameter as an index associated with a candidate beam, for example, after or in response to the base station receiving a preamble (e.g., a BFR preamble). The base station may determine and/or set a beam parameter of a DCI as an index of CSI-RS associated with a candidate beam. Additionally or alternatively, at step 3011, the base station may determine and/or set an indicator as a third value indicating that the beam parameter is for downlink beam failure recovery. The base station may determine and/or set an indicator of a DCI as the third value. At step 3012, the base station may send the indicator, and/or one or more messages comprising the indicator, to the wireless device. The base station may transmit the DCI, which may comprise the indicator, via a downlink control channel. One or more beam information fields may comprise one or more parameters indicating one or more: CSI-RS resources or SS blocks that may be associated with one or more PRACH, for example, if an indication field in the one or more DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam failure recovery procedure.

Each indicator (e.g., a field in a DCI) for indicating beam information for a downlink beam management, a downlink beam failure recovery, or an uplink beam management, may have the same or similar size. A unified DCI format (e.g., same or similar size) for different beam procedures may reduce blind decoding attempts, for example, for a PDCCH at a wireless device receiver, and as a result, may save power for the wireless device.

FIG. 31 shows an example that may be performed by a wireless device, for example, for downlink beam management, downlink beam failure recovery, and/or uplink beam management. At step 3101, the wireless device may receive, from a base station, configuration parameters and/or control information. The wireless device may receive one or more messages comprising configuration parameters for one or more of: a downlink beam management procedure, a downlink beam failure recovery procedure, and/or an uplink beam management procedure. Additionally or alternatively, the wireless device may receive one or more control information that may indicate and/or command performing one or more of the downlink beam management procedure, the downlink beam failure procedure, and/or the uplink beam management procedure.

At step 3102, the wireless device may determine one or more procedures to perform, which may comprise a downlink beam management procedure (shown in path “A”), an uplink beam management procedure (shown in path “B”), or a downlink beam failure recovery procedure (shown in path “C”). The wireless device may determine the one or more procedures based on an indicator in one or more messages that it may have received from step 3101. A DCI may comprise an indicator, such as a beam type indicator, that the wireless device may use to determine the one or more procedures to perform, via paths “A”, “B”, or “C” associated with a first type, a second type, and a third type, respectively, of a beam type indicator. The wireless device may determine the one or more procedures based on a two-bit indicator to indicate one of among three procedures, or to indicator one or among up to four procedures. The wireless device may determine the one or more procedures based on a one-bit indicator to indicate one of two procedures. The wireless device may determine to perform a downlink beam management procedure (path “A” from step 3102) based on the wireless device receiving, from the base station, a first command indicating the downlink beam management procedure. The wireless device may determine to perform an uplink beam management procedure (path “B” from step 3102) based on the wireless device receiving a second command indicating the uplink beam management. The wireless device may determine to perform a downlink beam failure recovery procedure (path “C” from step 3102) based on the wireless device detecting a beam failure.

At step 3103, if a determination is made to perform a downlink beam management procedure (path “A” from step 3102), the wireless device may initiate downlink beam management and/or transmit a beam report. The wireless device may transmit, via one or more uplink channels (e.g., PUCCH and/or PUSCH), one or more beam reporting information. The wireless device may transmit the one or more beam reporting information based on or in response to receiving one or more configuration parameters and/or control information indicating that the wireless device is to perform a downlink beam management procedure. The beam reporting information may comprise parameters indicating one or more downlink reference signals, and/or measurement quality of the one or more downlink reference signals.

At step 3104, the wireless device may monitor a downlink control channel for downlink control information (DCI). At step 3105, the wireless device may detect DCI comprising one or more beam parameters and an indicator. At step 3106, the wireless device may determine, based on the DCI, a type of procedure. The DCI may comprise one or more beam information fields and an indication field (e.g., indicator, or beam procedure type field). The indication field may indicate a beam procedure, such as a downlink beam management procedure, a downlink beam failure recovery procedure, or an uplink beam management procedure. By indicating the beam procedure, the indication field may indicate that the one or more beam information fields comprises one or more beam parameters for the respective beam procedure, for example, a downlink beam management procedure, a downlink beam failure recovery procedure, or an uplink beam management procedure.

At step 3107, if a determination is made for a downlink beam management procedure (path “X” from step 3106), the wireless device may adjust a receiving beam according to or based on one or more beam parameters that may be associated with the downlink beam management procedure. The one or more beam parameters may indicate an index of SSB or CSI-RS associated with a serving beam. The wireless device may complete the downlink beam management procedure. The procedure may end, for example, after step 3107, or the procedure may repeat, for example, returning to step 3101.

At step 3108, if a determination is made to perform an uplink beam management procedure (path “B” from step 3102), the wireless device may initiate uplink beam management and/or transmit one or more SRSs. The wireless device may transmit one or more uplink reference signals (e.g., SRSs). The wireless device may transmit the one or more uplink reference signals based on or in response to receiving one or more configuration parameters and/or control information indicating that the wireless device is to perform an uplink beam management procedure. The one or more uplink reference signals may be allocated in or determined based on one or more configuration parameters and/or control information. After step 3108, the wireless device may perform steps 3104, 3105, and 3106 as described above.

At step 3109, if a determination is made for an uplink beam management procedure (path “Y” from step 3106), the wireless device may adjust a transmitting beam according to or based on one or more beam parameters that may be associated with the uplink beam management procedure. The one or more beam parameters may indicate an index of one or more SRSs. The wireless device may complete the uplink beam management procedure. The procedure may end, for example, after step 3109, or the procedure may repeat, for example, returning to step 3101.

At step 3110, if a determination is made to perform a downlink beam failure recovery procedure (path “C” from step 3102), the wireless device may initiate beam failure recovery and/or transmit one or more PRACH transmissions (e.g., a PRACH preamble). The wireless device may transmit, via one or more uplink signals (e.g., PRACH, and/or PUCCH), beam information. The wireless device may transmit the beam information based on or in response to a detection of a downlink beam failure event. The beam information may comprise parameters indicating one or more downlink reference signals. The one or more uplink signals may be allocated in or determined based on one or more configuration parameters and/or control information. After step 3108, the wireless device may perform steps 3104, 3105, and 3106 as described above.

At step 3111, if a determination is made for a beam failure recovery procedure (path “Z” from step 3106), the wireless device may adjust a receiving beam according to or based on one or more beam parameters that may be associated with the downlink beam failure recovery procedure. The one or more beam parameters may indicate an index of CSI-RS or CSI-RS associated with a candidate beam. The wireless device may complete the downlink beam failure recovery procedure. The procedure may end, for example, after step 3111, or the procedure may repeat, for example, returning to step 3101.

The DCI may comprise, for example, a field for indicating parameters of one or more resource assignment. The field for indicating parameters of one or more resource assignment may indicate the one or more resource for a PDSCH resource assignment, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam management procedure. Additionally or alternatively, the field for indicating parameters of one or more resource assignment may indicate the one or more resources for a PDSCH resource assignment, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam failure recovery procedure. Additionally or alternatively, the field for indicating parameters of one or more resource assignment may indicate the one or more resource for a PUSCH resource assignment, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the uplink beam management procedure. The wireless device may adjust its transceiver parameters for PDSCH receiving, for example, if the field for the one or more resource assignment is for the PDSCH resource allocation. The transceiver parameters may comprise the receiving beam parameters based on the one or more beam information fields in the DCI. The wireless device may adjust its transceiver parameters for PUSCH transmission, for example, if the field for the one or more resource assignment is for the PUSCH resource allocation. Transceiver parameters for the wireless device may comprise the transmit beam parameters based on one or more beam information fields in the DCI.

The DCI may be used for cross-carrier scheduling in carrier aggregation. A base station may transmit one or more RRC messages comprising configuration parameters of at least one of a plurality of cells and a plurality of control resource sets. Each control resource set may be associated with one or more control resource parameters. The one or more control resource parameters may comprise one or more of a first OFDM symbol; a number of consecutive OFDM symbols; a set of resource blocks; a CCE-to-REG mapping; or a REG bundle size. The DCI may comprise one of a carrier indicator that may indicate the component carrier to which the DCI may be related, and a control resource set indicator.

The carrier indicator in the DCI may indicate a component carrier to which the DCI may be related, for example, if wireless device is configured with multiple component carriers. The carrier indicator may indicate the carrier via which a wireless device may perform the downlink beam management procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam management procedure. The carrier indicator may indicate the carrier via which a wireless device may perform the downlink beam failure recovery procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam failure recovery procedure. The carrier indicator may indicate the carrier via which a wireless device may perform the uplink beam management procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the uplink beam management procedure.

The control resource set indicator in the DCI may indicate a control resource set of a bandwidth part to which the DCI may be related. The control resource set indicator may indicate the bandwidth part a wireless device may use to perform the downlink beam management procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam management procedure. The control resource set indicator may indicate the bandwidth part a wireless device may use to perform the downlink beam failure recovery procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the downlink beam failure recovery procedure. The control resource set indicator may indicate the bandwidth part a wireless device may use to perform the uplink beam management procedure, for example, if the indication field in the DCI indicates the one or more beam information fields comprise one or more beam parameters for the uplink beam management procedure.

A wireless device may receive at least one radio resource control (RRC) messages comprising: one or more first parameters for a downlink beam failure recovery procedure; and one or more second parameters for an uplink beam management procedure. The wireless device may perform at least one of the downlink beam failure recovery procedure or the uplink beam management procedure. The wireless device may receive, from a base station via a physical downlink control channel (PDCCH), downlink control information (DCI) comprising: one or more beam information fields; and an indication field indicating whether the one or more beam information fields comprises one or more beam parameters for the downlink beam failure recovery procedure or the uplink beam management procedure. The wireless device may adjust one or more transceiver parameters based on the DCI. The one or more first parameters may comprise one or more of: SS blocks that may be associated with a SS block index (SBI), CSI-RS that may be associated with a CSI-RS resource index (CRI), QCL parameters, measurement settings, and/or reporting settings. The one or more second parameters may comprise one or more of: SRS configurations, each of which may be associated with a SRI (SRS Resource index), QCL parameters, and/or SRS power control commands.

A system comprising a base station and a wireless device may perform a downlink beam failure recovery procedure, for example, by the base station transmitting to the wireless device one or more beams associated one or more SS blocks or CSI-RS resources; performing measurements based on the one or more downlink beams; transmitting at least one of the one or more SBIs or CRIs associated with one or more downlink beams; and transmitting one or more CRIs. The system may perform uplink beam management procedure, for example, by the base station transmitting a DCI, triggering an uplink beam management; transmitting, by the wireless device, at least one SRS on at least one UE transmit beams; and transmitting, by the base station, one or more SRIs.

The one or more beam information fields may comprise one or more of a CRI, or a downlink assignment of a physical downlink shared channel (PDSCH), for example, if the indication field indicates that the one or more beam information fields comprises the one or more beam parameters for the downlink beam failure recovery procedure. The one or more beam information fields may comprise one or more of an SRI, or uplink grant of a physical uplink shared channel (PUSCH), for example, if the indication field indicates that the one or more beam information fields comprises the one or more beam parameters for the uplink beam management procedure. The one or more transceiver parameters may comprise at least an uplink transmission beam, for example, if the indication field indicates that the one or more beam information fields comprise the one or more beam parameters for the uplink beam management procedure. The one or more transceiver parameters may comprise a downlink receive beam, for example, if the indication field indicates that the one or more beam information fields comprise the one or more beam parameters for the downlink beam failure recovery procedure.

A base station (e.g. a gNB) and/or a wireless device may perform any combination of a step and/or a complementary step of one or more of the steps described herein. Any step performed by a gNB may be performed by any base station. A core network device, or any other device, may perform any combination of a step, or a complementary step, of one or more of the above steps. Some or all of these steps may be performed, and the order of these steps may be adjusted. Additional steps may also be performed. Any base station described herein may be a current base station, a serving base station, a source base station, a target base station, or any other base station.

FIG. 32 shows general hardware elements that may be used to implement any of the various computing devices discussed herein, including, for example, the base station 401, the wireless device 406, or any other base station, wireless device, or computing device described herein. The computing device 3200 may include one or more processors 3201, which may execute instructions stored in the random access memory (RAM) 3203, the removable media 3204 (such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard drive 3205. The computing device 3200 may also include a security processor (not shown), which may execute instructions of one or more computer programs to monitor the processes executing on the processor 3201 and any process that requests access to any hardware and/or software components of the computing device 3200 (e.g., ROM 3202, RAM 3203, the removable media 3204, the hard drive 3205, the device controller 3207, a network interface 3209, a GPS 3211, a Bluetooth interface 322, a WiFi interface 3213, etc.). The computing device 3200 may include one or more output devices, such as the display 3206 (e.g., a screen, a display device, a monitor, a television, etc.), and may include one or more output device controllers 3207, such as a video processor. There may also be one or more user input devices 3208, such as a remote control, keyboard, mouse, touch screen, microphone, etc. The computing device 3200 may also include one or more network interfaces, such as a network interface 3209, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 3209 may provide an interface for the computing device 3200 to communicate with a network 3210 (e.g., a RAN, or any other network). The network interface 3209 may include a modem (e.g., a cable modem), and the external network 3210 may include communication links, an external network, an in-home network, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 3200 may include a location-detecting device, such as a global positioning system (GPS) microprocessor 3211, which may be configured to receive and process global positioning signals and determine, with possible assistance from an external server and antenna, a geographic position of the computing device 3200.

The example in FIG. 32 is a hardware configuration, although the components shown may be implemented as software as well. Modifications may be made to add, remove, combine, divide, etc. components of the computing device 3200 as desired. Additionally, the components may be implemented using basic computing devices and components, and the same components (e.g., processor 3201, ROM storage 3202, display 3206, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components described herein may be implemented using computing devices having components such as a processor executing computer-executable instructions stored on a computer-readable medium, as shown in FIG. 32. Some or all of the entities described herein may be software based, and may co-exist in a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in a computer-usable data and/or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other data processing device. The computer executable instructions may be stored on one or more computer readable media such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. The functionality of the program modules may be combined or distributed as desired. The functionality may be implemented in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more features of the disclosure, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A module may be an isolatable element that performs a defined function and has a defined interface to other elements. The modules may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e., hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript. Additionally or alternatively, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware may comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors may be programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDs may be programmed using hardware description languages (HDL), such as VHSIC hardware description language (VHDL) or Verilog, which may configure connections between internal hardware modules with lesser functionality on a programmable device. The above mentioned technologies may be used in combination to provide a functional module.

Systems, apparatuses, and methods may perform operations of multi-carrier communications described herein. Additionally or alternatively, a non-transitory tangible computer readable media may comprise instructions executable by one or more processors configured to cause operations of multi-carrier communications described herein. An article of manufacture may comprise a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g., a wireless device, wireless communicator, a UE, a base station, and the like) to enable operation of multi-carrier communications described herein. The device, or one or more devices such as in a system, may include one or more processors, memory, interfaces, and/or the like. Other examples may comprise communication networks comprising devices such as base stations, wireless devices or user equipment (UE), servers, switches, antennas, and/or the like. A network may comprise any wireless technology, including but not limited to, cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or other cellular standard or recommendation, wireless local area networks, wireless personal area networks, wireless ad hoc networks, wireless metropolitan area networks, wireless wide area networks, global area networks, space networks, and any other network using wireless communications. Any device (e.g., a wireless device, a base station, or any other device) or combination of devices may be used to perform any combination of one or more of steps described herein, including, for example, any complementary step or steps of one or more of the above steps.

Although examples are described above, features and/or steps of those examples may be combined, divided, omitted, rearranged, revised, and/or augmented in any desired manner. Various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to be part of this description, though not expressly stated herein, and are intended to be within the spirit and scope of the disclosure. Accordingly, the foregoing description is by way of example only, and is not limiting. 

What is claimed is:
 1. A method comprising: receiving, by a wireless device, at least one radio resource control message comprising one or more parameters for: a downlink beam failure recovery procedure; and an uplink beam management procedure; receiving, via a downlink control channel, downlink control information (DCI) comprising: one or more beam information fields; and a beam procedure type field associating the one or more beam information fields with the downlink beam failure recovery procedure or the uplink beam management procedure; and adjusting, by the wireless device and based on the indication field, one or more transceiver parameters.
 2. The method of claim 1, further comprising initiating, by the wireless device and after detecting at least one beam failure based on the one or more parameters for a downlink beam failure recovery procedure, the downlink beam failure recovery procedure.
 3. The method of claim 1, further comprising initiating, by the wireless device and based on receiving a second DCI indicating a transmission of at least one sounding reference signal (SRS), the uplink beam management procedure, wherein the uplink beam management procedure comprises transmitting the at least one SRS based on the one or more second parameters.
 4. The method of claim 1, further comprising determining, based on the indication field, that the DCI comprises one or more of: a sounding reference signal resource index; or a channel state information reference signal resource index.
 5. The method of claim 1, wherein the at least one radio resource control message further comprises one or more parameters for a downlink beam management procedure, and the indication field further indicates that the one or more beam information fields comprises one or more beam parameters for the downlink beam management procedure.
 6. The method of claim 1, wherein the adjusting the one or more transceiver parameters comprises: adjusting receiving beams based on the one or more beam information fields of the DCI if the indication field of the DCI indicates that the one or more beam information fields comprises one or more beam parameters of the downlink beam failure recovery procedure.
 7. The method of claim 1, wherein the adjusting the one or more transceiver parameters comprises: adjusting transmitting beams based on the one or more beam information fields of the DCI if the indication field of the DCI indicates that the one or more beam information fields comprises one or more beam parameters of the uplink beam management procedure.
 8. The method of claim 1, wherein the one or more parameters of the downlink beam failure recovery procedure comprise one or more of: first reference signal (RS) resource parameters of a first plurality of reference signals (RSs); second RS resource parameters of a second plurality of RSs; or random access channel resources.
 9. The method of claim 1, wherein the one or more parameters of the uplink beam management procedure comprise one or more of: a bandwidth of a sounding reference signal (SRS); a numerology of the SRS; a frequency resource of the SRS; or a time resource of the SRS.
 10. The method of claim 1, wherein the one or more beam information fields comprise one or more of: a first bits field indicating a first RS index associated with one or more reference signals; a second bits field indicating a second RS index associated with one or more of a reference signal or a synchronization block.
 11. A method comprising: receiving, by a wireless device, at least one radio resource control message comprising one or more parameters for: a downlink beam failure recovery procedure; and an uplink beam management procedure; receiving, via a downlink control channel, downlink control information (DCI) comprising: one or more beam information fields; and a beam procedure type field associating the one or more beam information fields with the downlink beam failure recovery procedure or the uplink beam management procedure; and performing, by the wireless device and based on the beam procedure type field and the one or more beam information fields, either a downlink beam failure recovery procedure or an uplink beam management procedure.
 12. The method of claim 11, wherein the performing comprises initiating, by the wireless device and after detecting at least one beam failure based on the one or more parameters for a downlink beam failure recovery procedure, the downlink beam failure recovery procedure.
 13. The method of claim 11, wherein the performing comprises initiating, by the wireless device and based on receiving a second DCI indicating a transmission of at least one sounding reference signal (SRS), the uplink beam management procedure, wherein the uplink beam management procedure comprises transmitting the at least one SRS based on the one or more second parameters.
 14. The method of claim 11, further comprising: determining, based on the beam procedure type field indicating that the one or more beam information fields are associated with the uplink beam management procedure, that the DCI comprises one or more sounding reference signal resource indexes.
 15. The method of claim 11, further comprising: determining, based on the beam procedure type field indicating that the one or more beam information fields are associated with the downlink beam failure recovery procedure, that the DCI comprises one or more channel state information reference signal resource indexes.
 16. The method of claim 11, further comprising: adjusting receiving beams based on the one or more beam information fields of the DCI if the beam procedure type field of the DCI indicated that the one or more beam information fields are associated with the downlink beam failure recovery procedure.
 17. The method of claim 11, further comprising: adjusting transmitting beams based on the one or more beam information fields of the DCI if the beam procedure type field of the DCI indicates that the one or more beam information fields are associated with the uplink beam management procedure.
 18. A method comprising: transmitting, by a base station, at least one radio resource control message comprising one or more parameters for: a downlink beam failure recovery procedure; and an uplink beam management procedure; transmitting, via a downlink control channel, a downlink control information (DCI) comprising: one or more beam information fields; and a beam procedure type field associating the one or more beam information fields with the downlink beam failure recovery procedure or the uplink beam management procedure; and receiving, by the base station and based on the beam procedure type field, either a preamble for a downlink beam failure recovery procedure or a sounding reference signal for an uplink beam management procedure.
 19. The method of claim 18, further comprising: determining, based on the beam procedure type field associating the one or more beam information fields with the uplink beam management procedure, one or more sounding reference signal resource indexes for the DCI.
 20. The method of claim 18, further comprising: determining, based on the beam procedure type field associating the one or more beam information fields with the downlink beam failure recovery procedure, one or more channel state information reference signal resource indexes for the DCI. 